Skip to main content
Glama

referentiel_valeur

Read-onlyIdempotent

Valeur du référentiel (sourcée + datée) — La valeur 2026 d'une constante fiscale ou retraite par sa clé publique stable, avec sa source primaire, sa référence légale, sa date de vérification et son niveau de fiabilité. Jamais un chiffre nu. Clé inconnue → referentiel_recherche pour lister les clés disponibles. (sources: references_officielles.json v0.8.6)

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": {
      "cle": "<cle>"
    },
    "name": "referentiel_valeur"
  }
}

Input Schema

NameRequiredDescriptionDefault
cleYesClé publique stable (liste via referentiel_recherche). Ex. pass, cehr_seuil_celibataire, reversion_plafond_couple, carmf_rcv_valeur_point.
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).

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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds useful payload context ("Jamais un chiffre nu" plus source/legal reference/date/reliability), but it omits the payment gating that the teaser parameter implies — an agent could be surprised by a paid call. That is the key behavioral gap left unaddressed in the description.

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?

Front-loaded with the core promise, and the unknown-key routing sits where it is needed. The trailing "(sources: references_officielles.json v0.8.6)" is internal version metadata that does little for tool selection and could be dropped.

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?

No output schema exists, so the description must characterize the return value — and it does, enumerating source, legal reference, verification date and reliability level. For a 2-parameter read-only lookup this is nearly complete; only the cost/preview model is left to the schema.

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 description coverage is 100%, and the schema already defines cle with example keys and explains teaser as a free preview. The description's only added parameter meaning is that keys are stable/public and that unknown keys exist, which is marginal on top of the schema. Baseline 3 is appropriate.

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?

States a specific resource and scope: the 2026 value of a fiscal/retirement constant looked up by its stable public key. It also says what accompanies the value (primary source, legal reference, verification date, reliability level), which distinguishes it cleanly from the fiscal_* calculators that consume these constants.

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?

Gives an explicit routing rule for the failure case: "Clé inconnue → referentiel_recherche pour lister les clés disponibles." That is real when-to-use guidance. It stops short of saying when to prefer the domain calculators (fiscal_tmi, retraite_*) over this raw lookup, so no full alternative map.

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.