Skip to main content
Glama

Détail d'un bon

get_bon
Read-onlyIdempotent

Détails d'un bon + ses lignes d'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_bon"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant du bon de commande ou de livraison.

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 annotation set already declares readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the parenthetical "(Lecture seule.)" is largely redundant. The one piece of added behavioral context is that the response bundles the article lines with the header, which is genuinely useful and not in the annotations.

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?

Extremely short and front-loaded, with the substantive fact (lines included) first. The trailing "(Lecture seule.)" duplicates annotations and is the only wasted clause.

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?

With no output schema, the description does well to say that article lines are returned, but it says nothing about the shape of those lines, error behavior for an invalid id, or whether header fields are included. Adequate for a single-parameter read tool, but thin.

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 documented as an order-or-delivery-note identifier. The description adds nothing about the id (e.g. that it accepts either bon type) beyond what the schema already states, so 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 d'un bon + ses lignes d'articles" names a specific verb (retrieve details) and resource (bon) and adds the notable scope fact that article lines are included. It implicitly contrasts with list_bons but never names it, so sibling differentiation is left to inference.

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 when-to-use guidance at all: nothing says to use this when you already have an id versus when to call list_bons to search, and no prerequisites (valid id, existing bon) are stated.

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