well_upload_supplier_invoice_to_qonto
shallowio.github.WellApp-ai/well-mcp · Verify this server
Send one Well document to the workspace's connected Qonto account as a supplier invoice. When the user asks to send, push or upload an invoice to Qonto, first read the target workspace's Qonto input row with `well_get_connector_coverage({ slug: "qonto" })`. Call this tool only when its `connection_status` is `enabled` or `processing`, or when a projected `error` has non-null `sync_health`. A plain error row cannot send, even when `install_url` is null. List the documents and tell the user nothing was sent. Pass `document_id`: the Well document of the invoice (the PDF), never an invoice id. The user confirms on a card before the send. A document goes to one Qonto account once. A repeated call for the same document sends nothing and returns `outcome: "already_sent"`. Only the member who connected a Qonto account can send to it; a call by another member returns `outcome: "not_connection_owner"` and sends nothing. When the caller connected several Qonto accounts, the call returns `outcome: "connection_choice_needed"` with `workspace_connector_ids`: ask which one, then call again with `workspace_connector_id`. Tell the user the `message` the result carries. On `needs_reconnect`, ask the user to reconnect Qonto. On `failed`, say the send failed. On `unconfirmed`, say Well could not confirm the send and ask the user to check Qonto before a new try. On both, never say the invoice is in Qonto. 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.
1 trials · measured 1 day ago
well_upload_supplier_invoice_to_qonto scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.WellApp-ai/well-mcp, measured 18 Oct 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- gated
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-10-18 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 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.
[](https://vouch.tools/tools/f92c8a6c-a8ad-4fea-9c99-e86349a4176d)