Skip to main content
Glama

Check an invoice before it goes to the bank

well_verify_invoice_for_qonto
Read-onlyIdempotent

Check whether one invoice that Well issued can go to the workspace's connected Qonto account. It writes nothing and calls nothing in Qonto. Call it after the invoice is issued, before any send to Qonto.

Call well_send_invoice_to_qonto only when outcome is ready: its confirm is the one question to the person. already_imported means the invoice is in Qonto: ask nothing and send nothing. On not_connected and not_open, say nothing about Qonto.

Tell the person the message the result carries. On not_ready, say each reasons message; when a reason is operation_nature_missing, ask once whether the company sells goods, services or both, save the answer as default_operation_nature with well_upsert_accounting_settings, then call again; when that save is refused because the person is not an owner or admin, say that an owner or admin states it, and stop. On invoice_changed, check the invoice again; on ready, call the send again, so its confirm asks again. On needs_reconnect, give reconnect_url once. On connection_choice_needed, ask which Qonto account, then call again with workspace_connector_id. On not_connection_owner, say that only the member who connected Qonto can send to it.

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
invoice_idYesThe Well invoice to send to Qonto. Well must have issued it.
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.
workspace_connector_idNoThe Qonto connection to send to, only when several Qonto accounts are connected.

Output Schema

NameRequiredDescriptionDefault
errorNo
messageNo
outcomeNo
reasonsNo
successYes
reconnect_urlNo
invoice_numberNo
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.
qonto_invoice_idNo
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
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.
workspace_connector_idNo
workspace_connector_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, yet the description still adds real behavioral context: it writes nothing and makes no Qonto call, and it enumerates the outcome states that govern downstream actions (`already_imported`, `not_connected`, `not_open`, `needs_reconnect`, `not_connection_owner`). It also discloses permission behavior — a refused settings save means the person is not an owner or admin, and only the member who connected Qonto can send.

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?

Purpose, side-effect disclaimer and call ordering are front-loaded in the first three sentences, and the outcome branches follow in a consistent `on X, do Y` pattern. It is long and dense, and a few clauses (e.g. the `invoice_changed` re-send loop) could be tightened, but nearly every sentence maps to a distinct state the agent must handle.

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 five-parameter gate tool with an output schema and full read-only annotations, the description supplies exactly what the structured data cannot: when to call it, what to do with each outcome, and what to say to the person. Nothing needed to call it correctly or interpret a refusal 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 all five parameters are already documented, establishing a baseline of 3. The description goes beyond that by giving the decision rule for `workspace_id` ('when the token authorizes one workspace, call this directly… when it authorizes several ... pass `workspace_id`') and the trigger for `workspace_connector_id` ('ask which Qonto account, then call again with `workspace_connector_id`'). It adds no guidance for `conversation_id` or `workspace_scope`, leaving those to the schema.

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 and resource ('Check whether one invoice that Well issued can go to the workspace's connected Qonto account') and immediately scopes it as a pre-send gate. It explicitly separates itself from the sibling that performs the send (`well_send_invoice_to_qonto`), so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit call ordering ('Call it after the invoice is issued, before any send to Qonto') and names the alternative plus the condition that selects it ('Call `well_send_invoice_to_qonto` only when `outcome` is `ready`'). It also names a secondary alternative (`well_upsert_accounting_settings`) for the `operation_nature_missing` case and states stop conditions, which is the full when/when-not/alternative set.

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