Skip to main content
Glama

Détail d'une facture

get_invoice
Read-onlyIdempotent

Détails facture + articles. (Lecture seule.)

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>"
    },
    "name": "get_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la facture, du devis, de la proforma ou de la facture d'acompte.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the parenthetical "Lecture seule" merely restates that, adding no new behavioral context. The one genuine addition is that the response includes line items ("articles"), which is useful given there is no output schema, but permissions, errors, and record-not-found behavior remain undisclosed.

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?

Two short clauses, front-loaded with the resource and its payload. The parenthetical "(Lecture seule.)" is redundant with the readOnlyHint annotation and is the only wasted element.

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

Completeness3/5

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

For a one-parameter read tool with full schema coverage and safety annotations, the definition covers the essentials. However, with no output schema, it gives only a hint of the return payload ("articles") and says nothing about missing-record behavior or whether related entities are embedded.

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

Parameters3/5

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

Schema description coverage is 100% and the single id parameter is fully documented, including that it may identify a facture, devis, proforma, or acompte invoice — richer than the description itself. The description adds no meaning beyond the schema, so the baseline 3 applies.

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?

"Détails facture + articles" names a specific resource (invoice) and adds the notable detail that line items are included, so an agent knows this is a single-record detail fetch rather than a list. It does not explicitly differentiate itself from siblings such as get_credit_note or get_sale, which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives (e.g. get_credit_note, get_sale, list_* tools), nor any stated preconditions. "(Lecture seule.)" describes safety, not usage context, so the agent must infer the selection criteria entirely.

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