Skip to main content
Glama
Sign In

Marcel

by fr.marcel-retraite
OverviewDiscussionsAdmin

Comparer les rémunérations d'un dirigeant de SASU

compare_remuneration
Read-onlyIdempotent

Compare les voies de rémunération d'un dirigeant de SASU (salaire, dividende, mixte) pour un même bénéfice engagé. Porte sur ces voies sans PER ; avec un versement PER, voir simulate_remuneration_per. Entrées : bénéfice, niveaux de salaire, objectif, allocation chômage éventuelle. Sortie : net, droits à retraite et protection sociale de chaque voie. 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": {
      "beneficeDisponible": "<beneficeDisponible>"
    },
    "name": "compare_remuneration"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectifNoObjectif déclaré pour l'ordre d'affichage (défaut EQUILIBRE)
situationNo
eligiblePmeNoÉligible au taux réduit PME 15 % (défaut true)
partsFiscalesNoParts fiscales (défaut 1)
beneficeDisponibleYesBénéfice avant IS disponible dans la société
autresRevenusImposablesNoAutres revenus imposables du foyer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond that: it discloses the return content (net, droits à retraite, protection sociale per path) and a caveat that results are indicative and backed by reference cases. It does not discuss precision limits or edge cases in more depth, so not 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?

Three tight sentences: purpose and scope first, then the sibling exclusion, then inputs and outputs. Every sentence carries information; the only slight redundancy is restating the input list that the schema already covers.

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 correctly compensates by naming the returned metrics, and it flags the indicative nature of results. The nested 'situation' object and the enum-driven 'objectif' are left to the schema, which is acceptable at 83% coverage, though a note on how objectif affects ordering could have been added.

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 83%, so the schema already documents most parameters and the baseline is 3. The description's input list (bénéfice, niveaux de salaire, objectif, allocation chômage) adds little beyond the schema, and 'niveaux de salaire' does not correspond to any actual parameter, which is a minor mismatch rather than added meaning.

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 (Compare) and resource (voies de rémunération d'un dirigeant de SASU: salaire, dividende, mixte) with the scope constraint 'pour un même bénéfice engagé', and explicitly names the sibling it is not (simulate_remuneration_per). An agent can distinguish it from the many simulate_* siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: this tool covers the non-PER paths, and 'avec un versement PER, voir simulate_remuneration_per' names the alternative and the condition that selects it. It also enumerates the expected inputs, so the agent knows what to supply.

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