Skip to main content
Glama
MCP Toolkit

MCP Toolkit

timestamp_convert

Convert ISO 8601 timestamps or Unix milliseconds into UTC ISO and Unix seconds/milliseconds for consistent time comparisons and logging.

Instructions

Convert an ISO 8601 timestamp or Unix milliseconds to UTC ISO and Unix seconds/milliseconds.

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": {
      "value": "<value>"
    },
    "name": "timestamp_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the output encodings (UTC ISO plus Unix seconds and milliseconds), which is useful, but it says nothing about the shape of the response, rounding/precision, handling of ambiguous numeric input (seconds vs milliseconds), or behavior on invalid/non-parseable values.

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?

A single front-loaded sentence with no filler: it states the accepted inputs and the produced outputs in one pass. Nothing is redundant or buried.

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?

For a one-parameter, annotation-free, output-schema-free utility, the description covers both the input encodings and the output encodings, which is most of what an agent needs. It falls short only on error behavior and the exact shape of the returned values.

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 description coverage is 0% and the single parameter is an undescribed oneOf of string/number. The description compensates well by mapping the string form to ISO 8601 and the numeric form to Unix milliseconds, giving real semantics beyond the bare schema, though it never names the parameter or warns that seconds-valued numbers would be misinterpreted.

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 uses a specific verb ("Convert") plus the exact resource and both source encodings (ISO 8601, Unix milliseconds), so the tool's function is unmistakable. It does not explicitly contrast with siblings, but the siblings (base64, json, sha256, url) are in unrelated domains, so differentiation is largely implicit.

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 only implied: an agent can infer this is the tool for timestamp normalization from the name and the listed encodings. There is no statement of when to prefer it, no exclusion of related cases (e.g., other date formats, time zone conversion), and no prerequisites.

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