Hopi

Unix timestamp converter

hopi_unix_timestamp_converter

Read-onlyIdempotent

Convert between Unix epoch timestamps and readable dates. Pass a timestamp to get the UTC and local date (seconds or milliseconds detected automatically), or pass a date (and optional time, interpreted in local time) to get the timestamp in seconds and milliseconds. Source: https://hopi.co.uk/unix-timestamp-converter/

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	A date as YYYY-MM-DD. Provide this to convert a date to a timestamp.
`time`	No	Optional time as HH:MM:SS to accompany 'date' (default 00:00:00), in local time.
`timestamp`	No	A Unix timestamp in seconds or milliseconds (may be negative). Provide this to convert a timestamp to a date.

Output Schema

TableJSON Schema

Name	Required	Description
`iso`	No
`utc`	No
`unit`	No
`local`	No
`summary`	Yes
`relative`	No
`direction`	No
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026
- addedOutput schema / required
```
Added value: +[
+  "source_url",
+  "summary"
+]
```
First observedSep 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds meaningful behavioral context: automatic detection of seconds vs milliseconds, return of both UTC and local dates, local-time interpretation for date input, and production of both seconds and millisecond timestamps. No contradiction exists.

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 dense sentences front-load the purpose, then give mode-specific usage directives and timezone semantics. There is no filler, and the source URL is a small useful addition rather than clutter.

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

Completeness5/5

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

For a two-mode conversion tool with an output schema and safety annotations, the description is complete: it covers both input modes, unit handling, timezone behavior, and output breadth. Nothing needed to invoke the tool correctly is missing.

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 100%, so baseline is 3. The description goes beyond the schema by clarifying that timestamps are auto-detected as seconds or milliseconds and that date/time input is interpreted in local time, adding real semantic value beyond the parameter descriptions.

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?

The description states a specific verb ('Convert') and a clearly bounded resource: Unix epoch timestamps and readable dates. It explicitly covers both conversion directions and mentions automatic unit detection, making it easy to distinguish from sibling tools like hopi_time_zone_converter or hopi_date_calculator.

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?

The description gives clear instructions on when to pass a timestamp versus a date, including the optional time parameter and local-time interpretation. It does not explicitly contrast itself with alternatives, so it stops short of a full 5, but it provides sufficient context for an agent to call it correctly.

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

All Hopi 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.

Resources

Need Help?