Skip to main content
Glama
Sign In

Sous La Gélule

by fr.souslagelule
OverviewDiscussionsAdmin

Chercher un produit

chercher_produit
Read-onlyIdempotent

Retrouve un complément alimentaire par son nom ou sa marque (accents et majuscules ignorés), avec son rang dans son comparatif et son prix par mois.

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": {
      "texte": "<texte>"
    },
    "name": "chercher_produit"
  }
}

Input Schema

NameRequiredDescriptionDefault
texteYesNom du produit ou de la marque, par exemple « Nat&Form bisglycinate ».
limiteNoNombre de produits (10 par défaut).
categorieNoPour chercher dans une seule catégorie (facultatif).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: matching is accent- and case-insensitive, and results carry the product's ranking within its comparison and its monthly price. It does not say what happens with zero matches or how results are ordered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single front-loaded sentence that packs the search key, the matching rule and the returned highlights with no filler. Nothing could be removed 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 three-parameter read-only lookup with no output schema, the description tells the agent what inputs are meaningful and what comes back (rank and monthly price), which largely substitutes for the missing output schema. Only the no-result and ordering behavior remain unspecified.

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 in the schema, including the default of 10 and the 1–50 bound for limite. The description restates the texte semantics (name or brand, accents/case ignored) but adds nothing about limite or categorie, 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 and resource ('Retrouve un complément alimentaire') plus the search key (nom ou marque) and the returned highlights (rang dans son comparatif, prix par mois). It is clearly a lookup-by-name search, though it never explicitly contrasts itself with siblings like classement or meilleur_choix.

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 only implied: the 'par son nom ou sa marque' framing suggests calling it when a product or brand name is already known, and the mention of rank/price hints at what it is good for. There is no explicit when-not-to-use or pointer to an alternative tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sous La Gélule toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources