Skip to main content
Glama

Meilleur choix d'une catégorie

meilleur_choix
Read-onlyIdempotent

Le produit que Sous La Gélule met en avant dans une catégorie (classement indépendant : forme et dose d'abord, puis prix par mois à quantité égale, boutiques vérifiées), les produits presque aussi bons et presque aussi peu chers, et, avec un budget, le mieux classé sous ce budget. Prix en euros, France.

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": {
      "categorie": "<categorie>"
    },
    "name": "meilleur_choix"
  }
}

Input Schema

NameRequiredDescriptionDefault
categorieYesIdentifiant ou nom de la catégorie, par exemple « magnesium », « vitamine-d », « omega-3 ». Voir lister_categories.
budget_par_moisNoBudget maximum par mois, en euros (facultatif).

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds real behavioral context: the ranking is independent, prioritizes form and dose before price, normalizes price per month at equal quantity, and only considers verified shops. It also discloses what comes back (top pick, almost-as-good/almost-as-cheap alternatives), which annotations cannot convey. A minor 5-gap is that it does not state tie-breaking or how many alternatives are returned.

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 a single dense sentence with nested parentheses that packs purpose, ranking method, alternatives, budget behavior and locale; nothing is strictly redundant, but the budget behavior and 'prix en euros, France' are tacked on rather than front-loaded, making it harder to parse on first read.

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 two-parameter, no-output-schema tool this is nearly complete: it explains what is returned and on what basis, and how the optional budget changes the result. What is missing is the shape of the response (how many near-equivalents, their ordering), which would matter given there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the baseline is 3, and the description earns an extra point by giving the budget parameter real meaning: it is a monthly ceiling in euros applied to the ranking, and prices are normalized per month at equal quantity. The categorie parameter's format is left to the schema, which already documents it and points to lister_categories.

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 names the resource and verb precisely: it returns the product the site highlights in a category, plus near-equivalents, plus a budget-constrained pick. It also states the ranking basis (forme et dose d'abord, puis prix par mois), so an agent can tell it apart from a plain ranking or search tool. It falls short of a 5 because the single convoluted sentence buries the budget variant and never names the sibling it contrasts with.

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 implied rather than stated: passing budget_par_mois selects 'le mieux classé sous ce budget', and omitting it yields the general top pick. There is no explicit when-to-use versus classement or chercher_produit, and no when-not-to-use guidance, leaving routing to inference from the sibling names.

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