well_create_workspace_invoice_design
shallowio.github.WellApp-ai/well-mcp · Verify this server
Make a built invoice template the workspace's own invoice design, after the user kept it. Call well_get_workspace_invoice_design_offer first, with the same document_id, and show the user what it returns: the legal mentions text, whether a logo was cut from the invoice, and the company that issued the invoice, named in words. When that company is not the workspace's own, say so. Call this tool only after the user saw the template beside the invoice it was built from, saw that list, and said to keep it. Ask the user, for each of the two, whether to keep it or remove it, and pass the answer: keep_logo and keep_legal_mentions are required and have no default. Never pass true for a logo or a text the user did not keep. Pass the issuer_relation and the offer_token that the read returned: a keep made on a different reading or a different offer is refused. Pass the template's document_id. The keep approves the template, so from then on every new invoice drafted in this workspace opens on this design and prints with it, except for a customer that keeps a design of its own; the result names those customers so you can offer to switch them. One draft can still take another design, and an issued invoice never changes. Keeping again replaces the workspace's design with the new one. Only a workspace owner or admin can keep a design. A kept legal mentions text is saved as a note of the workspace, unless the template prints none of it: then no note is saved and legal_mentions_note_id is null, so tell the user the mentions were not kept. A removed logo or text is left out of every invoice printed with the design. When the template still prints the removed mentions in a form that cannot be found line by line, the keep is refused: ask for a revision that removes them (well_create_invoice_template_revision), then keep that revision.
1 trials · measured 1 day ago
well_create_workspace_invoice_design 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/e93c0c6c-aef3-4113-b129-e962c40655b7)