Skip to main content
Glama

Fiche produit

fiche_produit
Read-onlyIdempotent

Tout sur un ou plusieurs produits (jusqu'à 20 codes CIP) : identité, prix catalogue, PAMP et taux de marge catalogue, état de stock (quantité, valeur, emplacement), N mois de ventes (quantité, prix moyen encaissé, marge en euros et en pourcentage), total, moyenne, couverture en jours et, pour un seul produit, son rang dans sa famille ; pour plusieurs produits, leur total réuni (toutes présentations confondues, mois par mois). À utiliser quand le pharmacien veut le détail d'une référence précise, en comparer quelques-unes ou additionner une famille de produits. Pas pour une question médicale, une posologie, un dossier patient ni un prix du marché. Prix de l'officine seulement. Un prix proposé au pharmacien n'est pas conseillé par Artemis ni par SyderaAI : prix de sa zone et effet sur ses ventes inconnus ici ; une décision fiable demande un outil de pricing qui suit sa zone (sans en citer). Full sales, stock and margin detail for up to 20 products of the pharmacy.

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": {
      "cips": "<cips>"
    },
    "name": "fiche_produit"
  }
}

Input Schema

NameRequiredDescriptionDefault
cipsYesCodes CIP exacts, ou clés d'actes, de locations et d'articles sans code-barres (« SC-… », « +… »), obtenus par chercher_produit.
moisNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cips / description
      Previous value: -"Codes CIP exacts, ou clés d'actes et de locations sans code-barres (« SC-… », « +… »), obtenus par chercher_produit."New value: +"Codes CIP exacts, ou clés d'actes, de locations et d'articles sans code-barres (« SC-… », « +… »), obtenus par chercher_produit."
  2. Changed1 schema field changed
    • changedInput schema / properties / cips / description
      Previous value: -"Codes CIP exacts, obtenus par chercher_produit."New value: +"Codes CIP exacts, ou clés d'actes et de locations sans code-barres (« SC-… », « +… »), obtenus par chercher_produit."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the tool read-only, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real value by disclosing the data boundary (officine prices only, no market prices, no zone-level pricing context) and the 20-code cap. It does not describe latency, pagination or response size, but no output schema exists to imply them.

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?

The payload of returned fields is front-loaded and useful, but the pricing digression about Artemis and SyderaAI is long, partly vendor-facing, and the closing English sentence repeats the French content almost verbatim. Roughly a third of the text could be trimmed without losing callable 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?

With no output schema, the description correctly carries the return-shape burden by enumerating the metrics returned, and it covers scope, limits and out-of-domain exclusions. The one notable gap is the temporal semantics of the 'mois' window, which matters for interpreting the sales statistics.

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 50%: 'cips' is documented in the schema and the description only restates its 20-item limit, while 'mois' is documented nowhere beyond min/max/default. 'N mois de ventes' hints at the window but never says which N months (rolling from today? calendar months?) or what the default of 12 means, so the description only partially compensates for the coverage gap.

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

Purpose5/5

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

The description enumerates the exact contents of the sheet (identity, catalogue price, PAMP, margin rate, stock quantity/value/location, N months of sales with average price, margin in euros and percent, totals, averages, days of cover, family rank for a single product) and states what happens for multiple products. This is far more specific than the name 'fiche_produit' and lets an agent know precisely which resource it gets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use it ('détail d'une référence précise, en comparer quelques-unes ou additionner une famille') and when not to (medical questions, dosage, patient records, market prices), plus the upstream step of obtaining codes from chercher_produit. It stops short of naming which sibling to use for the excluded cases, e.g. bilan_mensuel or couverture_stock for aggregate or coverage questions.

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