Skip to main content
Glama

Stock faible

get_low_stock_products
Read-onlyIdempotent

Produits en stock faible. (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_low_stock_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNombre maximum de produits renvoyés (défaut 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/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 by structured data. The parenthetical "(Lecture seule.)" merely restates readOnlyHint and adds no new behavior. Crucially, the description never defines what 'stock faible' means (a threshold? a configured minimum? replenishment level?), which is the one behavioral fact an agent actually needs.

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?

It is short and front-loads the resource, which is good. However, the second fragment is a redundant repetition of an annotation rather than useful information, and the brevity here reflects under-specification rather than tight editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool itself is simple (one optional param, no output schema, rich annotations), but the description omits the defining criterion — what threshold makes a product 'low stock' — leaving the agent unable to interpret or explain results. No ordering or result-shape hints are given either, though the annotations do cover safety.

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?

There is a single optional parameter with 100% schema description coverage, including type, default (20) and meaning, so the schema does the heavy lifting. The description adds nothing about the limit — no mention of pagination, maximum value, or ordering of results. Baseline 3 applies when the schema is already complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Produits en stock faible" names a specific resource and a filter condition, so an agent can tell roughly what comes back. But there is no verb and no differentiation from near-siblings such as get_stock_alerts, get_stock_report or get_top_products, which also concern stock. It is vague on where the boundary lies between a 'low stock product' listing and a stock alert/report.

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 description contains no when-to-use guidance at all — no conditions, no prerequisites, and no mention of an alternative tool. The sibling list contains several overlapping stock tools, and the description does nothing to route the agent between them.

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