get_conversation

shallow

com.simafri/professional-email · Verify this server

Reads one thread whole: every message in order with its direction, its language and its attachments, the contact fiche, the mailbox the thread arrived through, the draft awaiting review when there is one, and in "notes" what the team left on the thread for each other, oldest first, with who wrote each one. Notes are never part of "messages" and were never sent to anyone. A message the mailbox sent carries "delivery" when the mail system tracked it: per recipient (Bcc included), "state" is "delivered" (accepted by the recipient's server, which says nothing of the inbox or of reading), "deferred" (retried by itself for five days), "bounced", "returned" (accepted, then a non-delivery report came back) or "expired", with the server's own "remote_reply" and a "reason" in plain words. When the thread was filed as it arrived, "filed_reason" says why: "spam_filter" for the filter's verdict, "blocked_sender" for a sender the account had reported, and "spoofed_own_domain" for a mail showing one of the account's own domains whose DMARC check failed, which lands in Spam in a mailbox (mark_not_spam takes it back out) and, on a helpdesk queue, in the Trash with its ticket closed (file_conversation with "inbox" brings it back, open). Read this before writing an answer. To read several threads, give conversation_id the list of their ids, in ONE call rather than one call per thread: the answer then lists in "results" the outcome of each thread in the order given ("ok", with its "result" or its "error") and counts "succeeded" and "failed". Each thread passes exactly the checks it would alone, so one refused or out of reach ("not found") leaves the others done, and the call is an error only when none succeeded.

100.0/100

1 trials · measured 10 days ago

get_conversation scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.simafri/professional-email, measured 12 Nov 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
gated
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-11-12100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: get_conversation
[![Vouch score](https://vouch.tools/api/tools/d52db6c2-deaa-4057-87e9-61fee57dc89f/badge.svg)](https://vouch.tools/tools/d52db6c2-deaa-4057-87e9-61fee57dc89f)
get_conversation — Vouch