Time MCP Server

get_time_ago

Read-onlyIdempotent

Calculate the exact date and time a specified number of days, hours, minutes, and seconds before now in a chosen timezone, with optional UTC output.

Instructions

Get the time a given number of days, hours, minutes and seconds ago in a specific timezone

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_time_ago"
  }
}

Input Schema

Name	Required	Description	Default
`utc`	No	Return UTC instead of the local or explicitly supplied timezone.
`days_ago`	No	Whole days before now
`timezone`	No	IANA timezone name (e.g., 'America/New_York', 'Europe/London'). Optional: defaults to the server's local timezone, 'Etc/UTC', when omitted.	Etc/UTC
`hours_ago`	No	Whole hours before now
`minutes_ago`	No	Whole minutes before now
`seconds_ago`	No	Whole seconds before now

Output Schema

Name	Required	Description	Default
`is_dst`	Yes
`datetime`	Yes
`timezone`	Yes
`day_of_week`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2026.11.11Nov 13, 2026

TDQS

B3.2/5.0

Behavior3/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 only that the offset is applied 'ago' from now; it does not mention that negative offsets are impossible (minimum: 0), how the timezone default resolves, or that an output schema exists. Adequate but thin beyond annotations.

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?

A single well-formed sentence that front-loads the verb and enumerates the offset dimensions. No filler, though it spends little of its length on anything an agent couldn't get from the schema.

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

Completeness3/5

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

With an output schema present and 100% schema coverage, the description needn't explain return values, and annotations carry safety. What's missing for a 6-parameter, all-optional tool is any statement of default behaviour (zero offsets), combination semantics, or sibling routing—moderate gaps only.

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 coverage is 100% and each parameter is documented in-schema, including the utc/timezone interplay, so the description need only reinforce the additive nature of the four offsets. It says 'days, hours, minutes and seconds ago' which implies combination, adding a little beyond the schema's per-field docs. Baseline 3 is appropriate.

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+resource: computes a past timestamp by offsetting from now by whole days/hours/minutes/seconds in a chosen timezone. It is clearly distinct from get_current_time and convert_time, though it never names a sibling to route against.

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?

No guidance on when to use this versus get_current_time or convert_time, and no note on behaviour when all offsets are left at their defaults (which presumably returns 'now'). The agent must infer the selection rule from the name alone.

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

Deploy Server