Skip to main content
Glama

Date difference

bursia_date_diff
Read-onlyIdempotent

Compute the time between two dates. Returns the difference in days, hours, minutes and milliseconds. Pure computation, free.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "bursia_date_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd date or datetime (ISO 8601).
fromYesStart date or datetime (ISO 8601), e.g. 2026-01-01.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / from / description
      Added value: +"Start date or datetime (ISO 8601), e.g. 2026-01-01."
    • addedInput schema / properties / to / description
      Added value: +"End date or datetime (ISO 8601)."
  2. First observed

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, closed-world, non-destructive, so the safety profile is covered. The description adds real value by stating the return shape (days, hours, minutes, milliseconds) despite there being no output schema, and by confirming no cost or side effects.

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?

Two tight sentences with the core operation front-loaded and the return units immediately after. No filler; every clause carries information.

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 two-parameter, read-only utility with no output schema, the description covers what it does and what it returns. Gaps remain around edge behavior (reversed date order, timezone assumptions, invalid input), but they are minor for this complexity level.

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% and both parameters are documented there as ISO 8601 start/end values. The description contributes nothing about parameter meaning, format edge cases, or ordering behavior, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Compute the time between two dates') and enumerates the units returned. It is clearly distinguishable from manipulation siblings like timestamp_convert, though it never names those alternatives explicitly.

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?

'Pure computation, free' implies a safe, costless call, and the purpose makes the use case inferable. But there is no explicit when-to-use guidance or exclusion versus bursia_timestamp_convert, bursia_timezone_convert, or bursia_semver_compare.

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