Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Unix Timestamp Converter

UnixTimestampConverter
Read-only

Unix Timestamp Converter: Unix Timestamp Converter converts Unix timestamps into formatted dates and parses ISO 8601 strings back into epoch seconds. Responses break down dates into ISO 8601, RFC 2822, simple time strings, individual calendar components like year, month and hour, plus the day of the year. Paid plans add the ISO week, and an IANA timezone to also get the same moment in local time with its UTC offset, abbreviation and daylight saving flag. (Cost: 1 credit)

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": "UnixTimestampConverter"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate string to convert (ISO 8601 format)
formatNoTimestamp formatseconds
timezoneNoIANA timezone (or fixed UTC offset) to also show the moment in, returned as a local block
timestampNoUnix timestamp to convert

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description usefully adds that responses include several date representations and that ISO week and IANA timezone local-time output are paid-plan features, plus a 1-credit cost; it stops short of explaining invalid input handling or other operational constraints.

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?

The main conversion behavior is front-loaded and the paragraph is reasonably efficient. However, the opening repeats the tool name twice and spends space enumerating output fields even though an output schema is present.

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?

Given the annotations, full schema coverage, and an output schema, the description provides enough context to call the tool correctly. It covers both conversion directions, the optional timezone behavior, paid-plan differences, and the credit cost.

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 the schema already fully documents the four optional parameters. The description adds some conceptual context around ISO 8601 input and timezone local-block output, but it does not add format choices, defaults, or constraints beyond the schema.

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?

The description states a specific verb and resource: it converts Unix timestamps to formatted dates and parses ISO 8601 strings back to epoch seconds. It is easy to tell what the tool does, though it does not explicitly distinguish itself from adjacent siblings like DateCalculator or TimezoneLookup.

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

Usage Guidelines3/5

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

Usage is implied by the description of converting timestamps and parsing ISO 8601 dates, but there is no explicit when-to-use guidance, no when-not-to-use cases, and no named alternative tools. The paid-plan note adds context but not selection guidance.

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

All APIVerve toolsInspect
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