MaCalculatriceEnLigne

calculate_time_difference

Compute the difference between two times or dates in seconds, minutes, hours, days. Use for project tracking, age, or scheduling. Inputs: start datetime, end datetime. Returns delta in multiple units. See list_bundles for related 'voyage' calculators.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city1`	Yes	First city
`city2`	Yes	Second city

Output Schema

TableJSON Schema

Name	Required	Description
`result`	No	Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
`source`	No	Authoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
`formula`	No	Human-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
`reference_url`	No	Link to a calcul2 page documenting the calculation in detail.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 13, 2026

TDQS

D1.7/5.0

Behavior1/5

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

Description claims it returns delta in multiple units, but no annotations provided. The contradiction between description (datetime inputs) and schema (city enums) creates serious confusion about actual behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, but the second sentence about 'list_bundles' is tangential and adds confusion rather than clarity. Not concise enough given the brevity.

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

Completeness1/5

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

With many sibling calculator tools, this tool's purpose is poorly defined due to the mismatch. Missing output description, and the reference to 'voyage' calculators suggests this might be a different calculation entirely.

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

Parameters1/5

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

Description says 'Inputs: start datetime, end datetime' which is completely contradicted by input schema expecting city1 and city2 with enum values. Schema coverage is 100% but description adds wrong information, making it worse than useless.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states the tool computes time difference between two times/dates, but input schema requires two city names (enum). This mismatch makes purpose unclear and misleading.

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

Usage Guidelines2/5

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

Only mentions usage contexts (project tracking, age, scheduling) and references sibling 'list_bundles' for voyage calculators. No guidance on when not to use or alternatives despite many similar sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MaCalculatriceEnLigne tools Inspect

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.