Skip to main content
Glama

Zéro problème : calculs du bailleur en France

Retard de restitution du dépôt de garantie

retard_restitution_depot
Read-onlyIdempotent

Calcule la date limite de restitution du dépôt de garantie d’une location d’habitation en France (un mois après la remise des clés si l’état des lieux de sortie est conforme à l’entrée, deux mois sinon) et la majoration de 10 % du loyer mensuel hors charges par mois de retard commencé (art. 22 de la loi du 6 juillet 1989). À utiliser pour « le propriétaire ne rend pas la caution », « pénalité retard dépôt de garantie », « délai restitution caution ».

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": {
      "loyer": "<loyer>",
      "depot": "<depot>",
      "date_remise_cles": "<date_remise_cles>",
      "etat_des_lieux_conforme": "<etat_des_lieux_conforme>"
    },
    "name": "retard_restitution_depot"
  }
}

Input Schema

NameRequiredDescriptionDefault
depotYesDépôt de garantie restant dû, en euros (après retenues justifiées).
loyerYesLoyer mensuel hors charges, en euros.
date_remise_clesYesDate de remise des clés, AAAA-MM-JJ.
date_restitutionNoDate de restitution effective, AAAA-MM-JJ. Absente : pas encore restitué, calcul à aujourd’hui.
etat_des_lieux_conformeYestrue si l’état des lieux de sortie est conforme à celui d’entrée (délai d’un mois), false sinon (deux mois).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish that the tool is read-only, idempotent, non-destructive, and closed-world. The description adds meaningful behavioral context beyond those annotations: the one-month versus two-month deadline depends on conformity of the exit inspection, and the penalty is 10% of monthly rent excluding charges per commenced month of delay.

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?

The definition is front-loaded with the core calculation, then states the legal rule and use cases. It is dense but efficient, with no redundant restatement of the title or schema.

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

Completeness5/5

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

For a read-only legal/financial calculator with a fully documented input schema and no output schema, the description covers the calculation rule, the conditional deadline, and the penalty formula. An agent has enough information to decide when to invoke it and how to interpret the result.

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 the input schema already explains all five parameters, including the optional effective return date and the meaning of the conformity boolean. The description reinforces how the conformity condition affects the deadline, but it does not add parameter syntax or constraints beyond what the schema provides.

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 states a specific calculation: the deadline for returning a rental security deposit in France and the related 10% monthly penalty. It names the legal basis (article 22 of the 6 July 1989 law), making the purpose unambiguous and distinct from unrelated sibling calculators.

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?

It gives clear intended-use contexts such as “le propriétaire ne rend pas la caution” and “délai restitution caution”, so an agent can tell when this calculator applies. It does not explicitly state when not to use it or name alternatives, but the siblings are different legal/financial calculators rather than near substitutes.

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.

Resources