Skip to main content
Glama

Meilleurs produits

get_top_products
Read-onlyIdempotent

Produits les PLUS ou les MOINS vendus sur N jours (caisse + factures définitives). order='desc' = meilleures ventes, order='asc' = pires ventes. Inclut aussi les produits JAMAIS vendus si include_unsold=true. (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_top_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoPériode : les N derniers jours, aujourd'hui compris (défaut 30).
sortNoClasser par quantité vendue ou chiffre d'affairesrevenue
limitNoNombre de produits renvoyés (défaut 10).
orderNodesc = plus vendus, asc = moins vendusdesc
include_unsoldNotrue = inclut les produits jamais vendus sur la période (0 vente)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description still adds real context: sales are counted from POS plus finalized invoices only, which affects what the numbers mean. '(Lecture seule.)' merely restates readOnlyHint and is dead weight.

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 tight sentences, front-loaded with the ranking behavior, then the parameter mapping. The closing '(Lecture seule.)' duplicates the annotation and could be dropped without loss.

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?

All five parameters are optional with defaults and fully documented in the schema, and the description explains the counting window and sources. With no output schema, a hint about the returned fields (product identity, quantity, revenue) is the main thing missing.

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% and every parameter already documents its default and meaning, so the schema carries the load. The description restates the order enum and the unsold flag rather than adding new semantics (e.g., how ties are broken or whether limit applies before or after filtering).

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?

Names a concrete resource (products) and a concrete operation (rank by most/least sold over N days), and pins down the data sources ('caisse + factures définitives') plus the unsold-products variant. It never explicitly contrasts itself with nearby tools, but the resource itself separates it from get_top_customers.

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?

The order='desc'/'asc' mapping tells the agent which mode to pick for best vs worst sellers, and include_unsold is given a clear condition. There is no guidance on when to choose this over get_product_sales_detail or get_stock_report, so the when-to-use story is only implied.

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