Skip to main content
Glama

referentiel_recherche

Read-onlyIdempotent

Recherche dans le référentiel — Liste les clés publiques du référentiel, filtrables par domaine (fiscal/retraite) et/ou par mot-clé. Renvoie un résumé par clé (valeur, libellé, fiabilité) ; utiliser referentiel_valeur pour le détail sourcé complet. (sources: references_officielles.json v0.8.6)

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": "referentiel_recherche"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoMot-clé cherché dans la clé publique ou le libellé.
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
domaineNoFiltre par domaine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / teaser
      Added value: +{
      +  "default": false,
      +  "description": "Aperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description adds the response shape (one summary per key with valeur, libellé, fiabilité) and provenance (references_officielles.json v0.8.6). It omits the payment dimension of the teaser flag, but that is documented in the schema.

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?

Two compact sentences that front-load the purpose, follow with the return shape, then the alternative. The trailing source-file/version parenthetical is minor provenance overhead but not harmful.

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 carries the burden of describing returns and does so adequately (per-key summary with value, label, reliability). The only real gap is the omission of the 'succession' domain value, which is a small but noticeable inconsistency for an agent choosing filters.

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 the baseline is 3. The description echoes the keyword and domain filters but lists only 'fiscal/retraite' while the enum also accepts 'succession', and it never mentions the teaser flag — so it adds little and is slightly incomplete relative to the schema.

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 gives a specific verb and resource ('Liste les clés publiques du référentiel') plus the two filtering axes, and names the sibling that returns full detail. An agent can distinguish this lookup/list tool from referentiel_valeur without inspecting either schema.

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 routes the agent to referentiel_valeur for full sourced detail, which is exactly the when-to-use distinction that matters here. It does not state any when-not conditions or prerequisites, so it falls just short of the top band.

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.