Skip to main content
Glama
Sign In

Marcel

by fr.marcel-retraite
OverviewDiscussionsAdmin

Comparer des scénarios patrimoniaux

marcel_compare_scenarios
Read-onlyIdempotent

Compare plusieurs scénarios d'un même profil : âge de départ, versements PER ou assurance-vie, loyers LMNP. Entrées : profil, actifs, liste de modifications par scénario. Sortie : résultat de chaque scénario et écarts, sans désignation d'une option. Changer l'âge ne recalcule pas la liquidation de la pension. 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": {
      "base": "<base>",
      "scenarios": "<scenarios>"
    },
    "name": "marcel_compare_scenarios"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYesSituation de base — net pension seulement si fiscaliserFoyer ou caller_provided
scenariosYesScénarios à comparer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare safe read-only/idempotent behavior, but the description adds non-obvious semantics: output includes each scenario and gaps without recommending an option; changing retirement age does not recalculate pension liquidation; results are indicatifs. These are material caveats beyond annotations.

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?

Four front-loaded sentences, each advancing purpose, input/output, a calculation caveat, and an accuracy caveat. There is 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?

No output schema exists, and the description does state that the return is per-scenario results plus écarts and no recommended option. For a complex nested input, the schema carries field detail, though the output shape could be slightly more explicit.

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 base and scenarios fields are already documented. The description maps inputs to profil/actifs/modifications and names examples matching enum values, but adds no extra syntax or constraints beyond 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 first sentence names a specific operation (comparer) and resource (scénarios d'un même profil), then enumerates the variation axes (âge de départ, versements PER/AV, loyers LMNP). This makes it distinguishable from single-scenario simulate_* siblings.

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?

It gives a clear implied use case—comparing multiple modifications for one profile—and lists example modification types. However, it never names when to choose it over sibling compare_* tools or when not to use it, so guidance stops at implied usage.

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