Skip to main content
Glama
Sign In

Marcel

by fr.marcel-retraite
OverviewDiscussionsAdmin

Calculer le financement d'un OBO

simulate_obo
Read-onlyIdempotent

Calcule un OBO (rachat de ses titres par une holding) : annuité, dividende remonté au régime mère-fille, taux de couverture de la dette, amortissement année par année et test de résistance. Entrées : valeur, apport, dette, taux, durée, dividendes. Sortie : tableau, couverture et viabilité du financement. 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": {
      "valeurOpCo": "<valeurOpCo>",
      "apportPersonnel": "<apportPersonnel>",
      "detteBancaire": "<detteBancaire>",
      "tauxDette": "<tauxDette>",
      "dureeDette": "<dureeDette>",
      "dividendeBrutAnnuel": "<dividendeBrutAnnuel>",
      "prixAcquisitionTitres": "<prixAcquisitionTitres>",
      "dureeDetentionTitresAns": "<dureeDetentionTitresAns>",
      "tmiDirigeant": "<tmiDirigeant>"
    },
    "name": "simulate_obo"
  }
}

Input Schema

NameRequiredDescriptionDefault
tauxDetteYesTaux annuel (ex: 0.04)
dureeDetteYes
tauxStressNoFacteur stress (ex: 0.80 = -20%, défaut 0.80)
valeurOpCoYes
tmiDirigeantYes
detteBancaireYes
apportPersonnelYes
dividendeBrutAnnuelYes
prixAcquisitionTitresYes
dureeDetentionTitresAnsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context: the calculation is backed by reference cases 'Marcel' and the result is explicitly 'indicatif', warning the agent not to treat it as authoritative.

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-loads the purpose, then inputs, then outputs and caveat in a single dense passage with zero filler. The input enumeration is slightly reductive but still earns its space by orienting the agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description appropriately sketches the return content (table, coverage, viability). However, for a 10-parameter financial model with three parameters undocumented anywhere, the definition is not complete enough for an agent to populate inputs confidently.

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?

With only 20% schema description coverage, the description should carry more weight. It names six conceptual inputs (valeur, apport, dette, taux, durée, dividendes) but leaves prixAcquisitionTitres, dureeDetentionTitresAns, tmiDirigeant and the optional tauxStress stress factor unexplained, and gives no units or required/optional distinction.

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 ('Calcule un OBO') and enumerates the concrete outputs (annuité, dividende remonté au régime mère-fille, taux de couverture, amortissement, test de résistance). No sibling tool covers an OBO, so the scope is unambiguous.

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 only implied by the tool name and OBO scope; there is no explicit 'use this when' and no mention of nearby alternatives such as simulate_rachat, simulate_apport_cession or simulate_mere_fille. An agent must infer positioning from domain knowledge.

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