Skip to main content
Glama

Mouvements de stock

list_stock_movements
Read-onlyIdempotent

Liste les mouvements de stock (entrées/sorties/ajustements) récents. (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_stock_movements"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoPériode : les N derniers jours, aujourd'hui compris (défaut 30).
typeNoin = entrées, out = sorties, adjustment = ajustements d'inventaire. Vide = tous.
limitNoNombre maximum de mouvements renvoyés (défaut 20).
product_idNoIdentifiant d'un produit : seulement ses mouvements. Vide = tous les produits.

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description's '(Lecture seule.)' merely restates readOnlyHint rather than adding context such as ordering, pagination behavior, or how far back 'récents' actually reaches. With annotations carrying the burden, the minimum-viable 3 is appropriate.

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 sentences with the resource and scope front-loaded; nothing is buried. The trailing parenthetical '(Lecture seule.)' is redundant with the annotations and slightly dilutes an otherwise efficient definition.

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 read-only list tool with four fully documented optional parameters and no output schema, the definition covers enough to call it correctly. Ordering of results and any cap on total retrievable movements are left implicit, but the schema-supplied defaults make this a minor gap.

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 schema already explains days, type, limit and product_id in detail, including defaults and the meaning of the enum values. The description's parenthetical list of movement kinds loosely mirrors the enum but adds no syntax, unit, or edge-case guidance beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb and resource ('Liste les mouvements de stock') and narrows scope with 'récents' plus a parenthetical enumeration of the movement kinds (entrées/sorties/ajustements). An agent can tell this apart from stock-alert or low-stock siblings by resource alone, but the description never explicitly contrasts itself with those alternatives.

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 only implied: the word 'récents' and the type enumeration suggest consulting a recent movement history, but there is no statement of when to prefer this over get_stock_alerts, get_stock_report, or get_low_stock_products. No preconditions or exclusions are given.

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