Skip to main content
Glama

Convert Unix timestamp to date

convert-unix-timestamp-to-date
Read-onlyIdempotent

Use when you need Unix timestamps as dates. Converts one or more timestamps, seconds or milliseconds, one per line, to UTC dates in ISO 8601 as a CSV. $0.01 USDC on Base per answer via x402; a refusal is 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": {
      "text": "<text>"
    },
    "name": "convert-unix-timestamp-to-date"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesOne or more Unix timestamps, one per line: whole seconds or milliseconds, digits with an optional leading minus, inside the years 0001 to 9999. At most 1,048,576 bytes of UTF-8 and 10,000 lines; a line break at the very end is not a line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that the tool is read-only, idempotent, non-destructive, and closed-world. The description adds valuable context beyond those annotations: per-answer pricing via x402, that refusals are free, and that output is CSV in ISO 8601. It stops short of detailing error behavior beyond refusals or output headers, but it is substantially more informative than the annotations alone.

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?

Three sentences, front-loaded with the usage condition and operation, followed by format/pricing details. Every sentence adds useful information and there is no redundant or filler wording.

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 simple one-parameter, read-only conversion tool, the description covers purpose, input expectations, output format, and payment behavior. With no output schema, it supplies the necessary return format context, and the schema handles detailed input constraints.

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?

The input schema already documents the single 'text' parameter completely, including line handling, units, allowed years, and size limits. The description repeats some of that (seconds or milliseconds, one per line) without adding new input semantics, so it sits at the baseline for high schema coverage.

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 names a specific verb and resource: convert Unix timestamps to UTC dates. It adds scope details (one or more timestamps, seconds or milliseconds, one per line) and output format (ISO 8601 CSV), making the operation unambiguous and distinguishable from unrelated siblings.

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 opening clause 'Use when you need Unix timestamps as dates' gives clear when-to-use guidance. It does not state when not to use the tool or name alternatives, but no sibling performs a similar conversion, so the omission is minor.

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