Skip to main content
Glama

Issue

solo_issue_invoice
Destructive

Make it real: freeze the seller and bill-to blocks, set the due date; the preview link becomes the document. Issuing is the point of no return (S-2): the seller block freezes from your company profile and the bill-to block from the customer (S-3), the due date is computed from the draft's terms, and the preview link becomes the document. Show the person the preview (doc_path) and the full numbers and get their confirmation BEFORE calling this. Refused without a company profile or a customer billing address — the refusal says what to gather. After: call solo_get_document and hand the person pdf_url — a direct download of the finished PDF; they send it themselves (S-7). Do not relay the bytes. Effects: invoice issued and immutable; seller and bill-to blocks frozen; document link final; PDF available.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "invoice_id": "<invoice_id>"
    },
    "name": "solo_issue_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoice_idYesThe draft to issue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description discloses the irreversibility ('point of no return'), exactly what becomes immutable (seller block, bill-to block, document link), how the due date is derived (from the draft's terms), and the refusal behavior including that the error text says what to collect. This is unusually rich behavioral context for a destructive tool.

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 core action and followed by preconditions, postconditions and an effects list, which is a sensible order for a destructive op. It loses a point for redundancy: 'the preview link becomes the document' appears twice and the effects list restates the frozen-blocks and final-link points, and the S-2/S-3/S-7 references add noise for an external reader.

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?

No output schema exists, and the description compensates by telling the agent what to call afterwards (solo_get_document) and which field to surface (pdf_url). Prerequisites, side effects and the confirmation workflow are all covered, so an agent can act correctly without further information.

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% and there is only one parameter, so the baseline is 3, but the description adds meaning the schema does not: the id must reference a draft, and issuing consumes that draft so its preview link becomes the permanent document. That state requirement is decision-relevant when picking an id.

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 ('issue' the draft invoice) and immediately delineates the state transition: the preview link becomes the real document. That cleanly separates it from solo_draft_invoice, solo_get_invoice and solo_void_invoice, which are preview/read/cancel operations.

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 explicit preconditions ('show the person the preview (doc_path) and the full numbers and get their confirmation BEFORE calling this'), explicit blocking conditions ('refused without a company profile or a customer billing address'), and explicit next steps ('after: call solo_get_document and hand the person pdf_url'). It also states a prohibition ('do not relay the bytes'), leaving nothing to inference.

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.