Skip to main content
Glama

retraite_regimes

Read-onlyIdempotent

Liste des régimes de retraite calculables par points — Découverte : renvoie les régimes en points calculables via retraite_pension_regime (code, libellé, machine, étage, valeur de service 2026, taux de réversion). Filtrable par famille. (sources: retraite_registre.js (source unique des 47 caisses) ; 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": "retraite_regimes"
  }
}

Input Schema

NameRequiredDescriptionDefault
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
familleNoFiltrer par famille (facultatif).

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=true, idempotentHint=true and openWorldHint=false, so safety behavior is covered. The description adds genuine context beyond that: the data is derived from a single registry of 47 caisses (retraite_registre.js) with a stated reference version (v0.8.6) and 2026 service values, signaling a versioned, static reference dataset rather than live computation. It does not discuss update cadence or staleness handling, which keeps it from a 5.

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?

The purpose and returned fields are front-loaded in a single dense sentence, with no redundant restatement of the title. The trailing parenthetical source citations (retraite_registre.js, references_officielles.json v0.8.6) are provenance notes that are useful but somewhat cluttering for an agent that mainly needs the behavior.

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 only two optional parameters, full schema coverage and annotations present, the description covers what is needed to invoke the tool correctly. Because there is no output schema, enumerating the returned fields is important and is handled well. The only minor gap is that the teaser parameter's output shape is left entirely 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%, so both parameters are already fully documented, including the enum values for famille and the meaning of teaser as a free preview. The description only echoes 'Filtrable par famille' and says nothing about teaser, adding essentially no meaning beyond the schema. Baseline 3 applies.

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 opens with a specific verb and resource ('Liste des régimes de retraite calculables par points') and then enumerates exactly what is returned (code, libellé, machine, étage, valeur de service 2026, taux de réversion). It explicitly ties the list to the calculation sibling retraite_pension_regime, so an agent can tell a discovery/catalog tool apart from an estimation tool without opening 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?

The 'Découverte' framing plus the reference to retraite_pension_regime makes the intended workflow clear: list/filter the eligible point-based regimes here, then calculate with the sibling. It states that results are filterable by famille. However, it never states when NOT to use it or what happens with an unknown famille, so the guidance is contextual rather than explicit.

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.