Skip to main content
Glama

Bons de commande et de livraison

list_bons
Read-onlyIdempotent

Liste les bons de commande (BCE) ou de livraison (BLE) émis. subtype: commande_envoye (BC vers fournisseur) ou livraison_envoye (BL vers client). (Lecture seule.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bons"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximum de bons renvoyés (défaut 20).
statusNobrouillon, envoye (envoyé), confirme (confirmé), partiellement_livre, livre (livré), facture (facturé) ou annule (annulé). Vide = tous.
subtypeNocommande_envoye = bons de commande envoyés aux fournisseurs, livraison_envoye = bons de livraison remis aux clients. Vide = les deux.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so "(Lecture seule.)" largely restates structured data. The genuinely additive content is the scoping word "émis" (only issued vouchers) and the subtype-to-business-document mapping; nothing is said about ordering, pagination behavior beyond the limit default, or what a returned bons looks like.

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 resource and followed by the subtype semantics; nothing is buried. The trailing "(Lecture seule.)" is the one largely redundant element given the annotations.

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 a simple, fully-optional three-parameter list tool with complete schema coverage and a clear read-only safety profile in annotations, the description covers purpose, subtype selection and status filtering context adequately. The only real gap is that no output schema exists and the description says nothing about the shape or ordering of returned records.

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 both enums are fully documented in the schema, including the same supplier/customer mapping and the "Vide = tous" / "Vide = les deux" semantics. The description's subtype explanation duplicates the schema rather than adding new meaning, 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?

The description names a specific verb ("Liste") and resource ("bons de commande (BCE) ou de livraison (BLE) émis"), and defines the two subtype variants, so an agent knows exactly what collection is returned. It stops short of naming a sibling it is not (e.g., list_deliveries), so the differentiation from adjacent list tools is only partial.

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?

Usage is implied rather than stated: it lists issued bons and says the subtype selects purchase orders to suppliers vs delivery notes to clients. There is no explicit when-to-use/when-not-to-use guidance and no routing to alternatives such as list_deliveries or get_bon for a single record.

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