Skip to main content
Glama
Sign In

Marcel

by fr.marcel-retraite
OverviewDiscussionsAdmin

Lire une règle du registre à une date

registre_reglementaire
Read-onlyIdempotent

Lit le registre réglementaire de Marcel : la règle en vigueur à une date, avec sa version, sa source officielle et sa valeur. Entrées : famille de règle (PFU_GENERAL, PS_GENERAL, IS_TAUX_NORMAL, PASS…), date. Sortie : règle, valeur, source, dates d'effet. Calcul couvert par des cas de référence Marcel : résultat indicatif.

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": {
      "family": "<family>"
    },
    "name": "registre_reglementaire"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate au format YYYY-MM-DD (défaut : aujourd'hui)
familyYesFamille de règle : PFU_GENERAL, PS_GENERAL, IS_TAUX_NORMAL, IS_TAUX_REDUIT, PER_DEDUCTION_ENTREE, PEA_PLAFOND, AV_ABATTEMENT, PASS, etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 a closed (openWorld=false) registry, so the baseline is low. The description still adds real value: it discloses the output shape (règle, valeur, source, dates d'effet) and the important caveat that results are 'indicatif' and covered only by reference cases.

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?

A single compact paragraph that front-loads the purpose before inputs and outputs. The 'Entrées/Sortie' listing is slightly formulaic but each clause carries information; no filler.

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 read-only lookup with no output schema, the description supplies the return fields and the indicative-calculation caveat, which is what an agent needs. It could go further on fallback behavior when a family or date has no matching rule, but the essentials are present.

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 both parameters are already documented in the schema, including the YYYY-MM-DD default of today. The description restates the family values and date without adding syntax or edge-case meaning, so 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?

States a specific verb and resource ('Lit le registre réglementaire de Marcel : la règle en vigueur à une date') and enumerates the returned fields, so an agent can tell this read-only lookup apart from the many simulate_*/compare_* siblings. The family enum examples (PFU_GENERAL, PS_GENERAL, PASS…) further pin down scope.

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 by 'la règle en vigueur à une date' — fetch the applicable rule at a point in time — but the description never states when to prefer this over the simulation tools or any prerequisites. No explicit when-not or alternative routing is given.

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

All Marcel 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