Skip to main content
Glama

Fiche produit

get_product
Read-onlyIdempotent

Détails d'un produit par ID. (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_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant du produit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so "(Lecture seule.)" merely restates structured data instead of adding to it. The description supplies no behavioral context of its own — not what a failed lookup returns, not whether archived products are visible, not the response shape.

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: the purpose comes first and the qualifier second. The parenthetical "(Lecture seule.)" earns little place since the annotations already state read-only status, but it is a trivial amount of waste.

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 getter with full schema coverage and complete annotations, the definition is minimally sufficient to call correctly. It is thin on what the agent gets back (no output schema exists) and on not-found or permission behavior, which are relevant for a per-ID detail tool.

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?

The single parameter is fully documented in the schema (100% coverage: "Identifiant du produit."), so the schema carries the load. "par ID" confirms the lookup semantics but adds no format or constraint detail beyond the schema, making the baseline 3 appropriate.

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 produit par ID" names a specific verb (retrieve details) and resource (produit) with the lookup key (ID). It is clear enough to separate this from list_* siblings and from get_product_sales_detail, though it does not name any sibling explicitly.

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?

The only usage signal is "par ID", which implies a single-record lookup, and no conditions are given for choosing this over get_product_sales_detail, get_low_stock_products, or get_top_products. There are no prerequisites, no exclusions, and no stated behavior when the ID is unknown.

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