Skip to main content
Glama

List suppliers silent since the mailbox stopped

well_list_silent_mail_suppliers
Read-only

When the workspace's mailbox stopped syncing, list the regular suppliers whose invoices came by mail before the stop and from whom no invoice came since. Use it for "find my missing receipts" or "retrouve mes justificatifs manquants" when the mailbox Well reads the supplier invoices from is stopped. It reads stored documents and connector states only: it reads no mailbox, no bank payment and no supplier site.

mailbox: state is "stopped" when every Gmail or Outlook install of the workspace stopped (its access expired, it errors or it was disconnected), "live" when one still syncs, "none" when none was ever connected. stopped_at is the last successful sync of the stopped mailbox (null when it never synced); stopped_service_ids names it.

suppliers: only for a stopped mailbox. A supplier is listed when its invoices came by mail on a cadence over the 12 months up to the stop, it still sent at the stop, its next invoice was due by today, and Well holds no invoice of it issued since the stop, by any route. Each has company_id, name, cadence (monthly, bimonthly, quarterly), months_received, last_received_at, usual_amount (the grand total of its last invoice; null when that invoice holds none) and currency. The largest cost per month comes first, at most 10; supplier_count counts them all. A supplier absent from the list sends on none of these cadences, a yearly one included, had stopped before the mailbox did, is not due yet, or something of it came since: never name it as silent. suppliers_truncated: true means the history hit its cap, so a silent supplier may be missing.

An empty suppliers with state: "stopped" means no regular mail supplier went silent, not that nothing is missing.

status: "failed" means the read failed: the mailbox state and the suppliers are unknown, never empty.

Every amount in the result is in the major units of its currency, never in cents: 1860 is 1,860.00 EUR, not 18.60 EUR.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
errorNo
statusYes
mailboxNo
successYes
suppliersNo
supplier_countNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
suppliers_truncatedNo
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description nonetheless adds real behavioral context: empty suppliers with state=stopped means nothing went silent, status=failed means unknown, amounts are in major units, and suppliers_truncated signals a cap hit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and clearly partitioned into mailbox/suppliers/edge-case blocks, so the length is mostly earned. Some sentences restate the same exclusion ('never name it as silent'), keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter, read-only query with an output schema, the definition covers the state machine, list-building criteria, truncation, empty-vs-failed distinction and amount units. Nothing an agent needs to call or interpret it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the closing paragraph adds routing meaning beyond the schema: omit workspace_id when the token authorizes one workspace and pass it when several are authorized, since the read will not guess.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (list) and a precisely scoped resource (regular suppliers whose invoices came by mail before the mailbox stopped and nothing since), and explicitly draws the negative space (reads stored documents and connector states only, not mailbox, bank payment or supplier site), which separates it from siblings like well_search_mailbox_for_receipt or well_list_missing_invoices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger with example utterances ('find my missing receipts' / 'retrouve mes justificatifs manquants') and the prerequisite condition (the mailbox Well reads supplier invoices from is stopped). It never names a sibling tool as the alternative, so the agent must infer routing itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources