utility-converter

convert_timestamp

Convert between Unix timestamps and human-readable datetimes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tz`	No	IANA timezone name used for display/interpretation. Defaults to "Asia/Seoul".	Asia/Seoul
`value`	Yes	For "to_datetime", a Unix timestamp in seconds (e.g. "1752300000"). For "to_timestamp", an ISO 8601 datetime (e.g. "2026-07-12 15:30:00"). The special value "now" returns the current time in both formats.
`direction`	No	"to_datetime" or "to_timestamp". Defaults to "to_datetime".	to_datetime

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 12, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are present, so the description carries full burden. It does not disclose behavioral traits such as timezone handling, side effects, or limitations (e.g., supported ranges, format strictness).

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?

Single sentence conveys the core purpose efficiently with no unnecessary words.

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?

Complexity is low with 3 well-documented parameters and an output schema present. The description is minimal but adequate given schema coverage; no critical gaps.

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%, so baseline is 3. The tool description adds no additional insight beyond what the schema already provides for parameters.

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?

Description clearly states the tool converts between Unix timestamps and human-readable datetimes, which is specific and distinguishes from sibling tools like calculate_date or convert_units.

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 is provided on when to use this tool versus alternatives. It lacks context about prerequisites or scenarios where conversion is appropriate.

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

All utility-converter tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.