Skip to main content
Glama

État du stock

get_stock_report
Read-onlyIdempotent

Rapport de stock officiel, chiffres identiques au module Gestion des stocks. section : overview (vue d'ensemble), movements (nombre de mouvements, entrées et sorties en quantité, produits les plus mouvementés), valuation (valorisation), alerts (alertes), performance (meilleures ventes). all_time=true pour tout l'historique. (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": "get_stock_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoPériode en jours (pour movements/performance)
sectionNooverview = vue d'ensemble, movements = mouvements (défaut), valuation = valorisation, alerts = alertes, performance = meilleures ventes.movements
all_timeNotrue = tout l'historique (ignore days)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the '(Lecture seule.)' note is largely redundant. The one piece of added context is the guarantee that figures match the Gestion des stocks module, which is useful trust information, but nothing is said about volume, pagination or 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, which is good, but the long parenthetical re-listing every section duplicates the enum descriptions in the schema and bloats a single sentence. Trimming the section recap would make it tighter without losing information.

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 read-only, three-parameter report tool with no output schema, the description covers what data is available, how to scope it by period, and how to get full history. Only the absence of any return-shape or size hint keeps it from being fully complete.

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 coverage is 100%, so all three parameters are already documented, including the enum values and the 'all_time ignores days' behavior. The description restates the section meanings and the all_time semantics 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?

States a specific verb+resource ('Rapport de stock officiel') and enumerates the five sections it can return, so an agent knows exactly what data it produces. It does not name or differentiate itself from siblings like get_low_stock_products or list_stock_movements, which overlap with the alerts and movements sections.

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?

Gives implied usage through the section list and the 'all_time=true pour tout l'historique' hint, which tells the agent how to widen the time window. It never says when to pick this tool over the more specialized siblings (e.g. get_stock_alerts, list_stock_movements), leaving that inference to the agent.

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