Skip to main content
Glama

Lexou · droit français

Calculer un délai de procédure

calculer_delai_de_procedure
Read-onlyIdempotent

Date d'expiration d'un délai en jours, mois ou années selon les articles 640 à 642 du Code de procédure civile : jours fériés et fins de semaine reportés au premier jour ouvrable, délai franc, augmentation pour l'outre-mer ou l'étranger, Alsace-Moselle. Rend la date et le raisonnement pas à pas. Pas pour un délai de prescription (il dépend de la nature de l'action).

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": {
      "depart": "<depart>",
      "duree": "<duree>",
      "unite": "<unite>"
    },
    "name": "calculer_delai_de_procedure"
  }
}

Input Schema

NameRequiredDescriptionDefault
dureeYesDurée du délai
francNoDélai franc : l'acte peut encore être fait le lendemain du dernier jour
uniteYes
departYesJour de l'événement qui fait courir le délai (notification, signification, décision)
distanceNoAppliquer l'augmentation de délai pour distance (article 643 et 644)
residenceNoLieu de résidence de la partie, pour l'augmentation pour distance
alsace_moselleNoJours fériés d'Alsace-Moselle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

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 behavioral context beyond that: weekend and public-holiday rollover to the first working day, franc deadline handling, overseas/foreign extensions, Alsace-Moselle holidays, and that it returns the date plus step-by-step reasoning.

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 core output (expiry date) and then the rules, ending with the exclusion. Dense but every clause carries information; the single long sentence is slightly heavy but not padded.

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 7-parameter calculation tool with no output schema, the description covers the return value (date + step-by-step reasoning) and the main rule variants. Minor gaps remain on how distance and residence interact, but the essentials for correct invocation are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the baseline is 3, but the description adds legal meaning to several parameters: 'délai franc', the distance extension for outre-mer/étranger, and Alsace-Moselle holidays. This helps an agent understand why franc, distance/residence and alsace_moselle exist, beyond the schema's own labels.

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 precise verb+resource (compute an expiry date for a procedural deadline) with the legal basis (articles 640-642 CPC) and the units supported. It also explicitly distinguishes itself from a prescription deadline, so an agent can tell it apart from related legal-calculation siblings.

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?

Gives a clear when-not ('Pas pour un délai de prescription') with the reason, which is strong routing guidance. It does not name an alternative tool to use instead, so it falls short of full when/when-not/alternatives coverage.

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