Skip to main content
Glama

Outil.io

Issue invoice

issue_invoice

Émettre, numéroter et figer une facture, générer son PDF et l’écriture de vente. Idempotent. N’envoie aucun message et ne transmet pas de facture électronique à une plateforme agréée.

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": {
      "id": "<id>",
      "version": "<version>"
    },
    "name": "issue_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior5/5

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

Annotations only declare it is a non-read-only, non-destructive, closed-world mutation. The description adds real behavioral context well beyond that: the invoice is numbered and frozen (irreversible state change), a PDF and an accounting entry are produced as side effects, the call is idempotent, and no messaging or e-invoicing transmission occurs.

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?

Three short sentences, front-loaded with the core action and followed by the two constraints an agent most needs. No filler, though the side-effect and exclusion clauses could be tightened slightly.

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

Completeness4/5

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

For an irreversible mutation with no output schema, the description covers side effects, retry safety, and explicit non-actions. It does not say what is returned (e.g. the assigned invoice number or PDF reference) or what happens when an already-issued version is passed, which would fully close the loop.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, yet it never mentions 'id' or 'version'. In particular it does not explain that 'version' is presumably an optimistic-concurrency guard that makes the idempotent/freeze semantics work. The parameters are simple and self-typed, which limits the damage, but the gap is real.

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

Purpose4/5

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

Uses specific verbs tied to the invoice resource: issue, number, freeze, generate PDF and the sales/accounting entry. An agent knows exactly what the operation produces. It stops short of naming a sibling (create_invoice, download_invoice_pdf) to contrast with, so it is clear but not sibling-differentiated.

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

Usage Guidelines3/5

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

The exclusions ('does not send any message, does not transmit an e-invoice to a certified platform') are genuinely useful scoping, and idempotency signals it is safe to retry. However, there is no explicit when-to-use statement or named alternative, so an agent must infer that this runs after create_invoice on a draft rather than instead of it.

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.