Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

convert_timestamp

Read-only

Convert Unix epoch timestamps to human-readable dates or parse date strings back to timestamps. Auto-detects seconds, milliseconds, ISO 8601, and other formats, returning UTC, local time, and calendar analysis.

Instructions

Unix Timestamp Converter. Convert a Unix epoch timestamp to a human-readable date, or parse a date string back to a Unix timestamp, with full UTC and local-time breakdowns. Auto-detects the input format: 10-digit Unix seconds, 13-digit Unix milliseconds, ISO 8601, or any parseable date string. Unlike time_iso_8601_formatter (which only parses and formats ISO 8601 / RFC 3339 strings) or time_date_difference (which measures spans between two dates), this tool centres on a single instant and emits every common representation of it at once. Requires a non-empty input; it does not fall back to the current time. Runs locally on the value you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns the detected format plus Unix seconds, milliseconds, ISO 8601, UTC, local strings, and a calendar analysis (weekday, day/week of year, quarter, leap-year flag, days in month, timezone offset, and a now-relative phrase that varies between cal

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe timestamp or date to convert. Accepts 10-digit Unix seconds, 13-digit Unix milliseconds, an ISO 8601 datetime, or any parseable date string. Must not be blank (also accepted under the keys timestamp or text).
nowNoOptional reference instant in Unix milliseconds used only to compute the relative phrase (for example 2 days ago). Omit to use the server current time, which makes the relative field vary between calls.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the conversion succeeded.
detectedFormatNoThe input format that was auto-detected (for example Unix Timestamp seconds, ISO 8601, or Date String).
resultsNoThe converted instant in multiple representations.
errorNoPresent only on a 400 error response; the failure reason.
Behavior5/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral details: runs locally, read-only, non-destructive, rate-limited (60 req/min for anonymous), and auto-detects formats. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and well-organized, but appears truncated at the end ('...varies between cal'). This indicates the provided text is incomplete, reducing conciseness and structure. Otherwise, it would be a 5.

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?

Despite truncation, the description covers input format auto-detection, output fields, constraints, behavioral traits, and alternative tools. Given the existence of an output schema, this is comprehensive.

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 adds useful context: the 'input' parameter also accepts alias keys ('timestamp' or 'text'), must not be blank, and the 'now' parameter is optional for relative phrases. This exceeds baseline.

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 clearly states 'Unix Timestamp Converter' and explains it converts between Unix epoch timestamps and human-readable dates. It auto-detects input formats and distinguishes itself from sibling tools like time_iso_8601_formatter and time_date_difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool vs alternatives by naming specific sibling tools and explaining differences. Also notes constraints: requires non-empty input and does not fall back to current time.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server