date_diffCompute the difference between two dates/times (UTC). Returns the signed difference in ms, seconds, minutes, hours, days and weeks, plus a human-readable summary. Accepts ISO-8601 (e.g. "2026-01-01" or "2026-01-01T12:00:00Z").
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | End date/time (ISO-8601). | |
| from | Yes | Start date/time (ISO-8601). |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "from": "2025-01-01T00:00:00Z",
+ "to": "2025-01-15T12:30:45Z"
+ },
+ {
+ "from": "2024-06-15",
+ "to": "2026-01-01"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe behavior. The description adds context about output (signed difference in multiple units, human-readable summary) and input format (ISO-8601), but does not disclose edge cases or error handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core function, no wasted words. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with full schema coverage and annotations, the description covers input format, output (multiple units + summary), and timezone (UTC). Missing details on error handling or non-valid inputs, but overall fairly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with each parameter described as 'date/time (ISO-8601)'. The description adds example formats but no new semantic meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Compute the difference' and the resource 'two dates/times (UTC)', and distinguishes itself from siblings like 'add_duration' and 'date_info' by specifying it returns signed differences in multiple units.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for date difference computation but does not explicitly state when to use this tool versus alternatives like 'add_duration' or 'date_info'. No when-not-to-use or alternative guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.