Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-unix-to-iso

Unix To ISO: Convert unix to iso. 🆓 5 free trial calls per signed wallet

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": "x402-unix-to-iso"
  }
}

Input Schema

NameRequiredDescriptionDefault
tsNo
timestampNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / timestamp / description
      Removed value: -"Timestamp to process"
    • removedInput schema / properties / ts / description
      Removed value: -"Ts to process"
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the payment model (5 free trial calls per signed wallet), which is genuinely useful, but says nothing about accepted timestamp units (seconds vs milliseconds), the ISO output format (Z suffix, offset, precision), or error behavior for invalid input. For a conversion tool with zero annotation coverage that is a substantial gap.

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 text is short and front-loaded, but the leading "Unix To ISO:" merely echoes the tool name and is immediately restated as "Convert unix to iso," so half the content is redundant. The promotional trial-call line consumes a meaningful share of an already tiny description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-param conversion with no output schema and no annotations, an agent still needs to know which parameter to populate, what units are expected, and what the ISO result looks like. None of that is present, leaving the definition inadequate for correct invocation despite the tool's low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Two parameters, ts and timestamp, both optional with 0% schema description coverage, create an ambiguity the description never resolves: which one should be used, whether they are aliases, and whether the value must be a string of digits. The description implies a unix timestamp input but adds no meaning beyond that implication.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Convert unix to iso" states a direction of conversion, but it is essentially an expansion of the name and adds no distinguishing detail against close siblings such as x402-iso-to-unix, x402-unix-to-date, or x402-epoch-to-date. An agent can guess the operation but cannot tell what makes this one different from the several other unix/date converters in the sibling list.

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?

There is no guidance on when to use this over x402-unix-to-date or x402-iso-to-unix, and no mention of prerequisites or expected input conditions. The only usage-adjacent sentence is a pricing note about free trial calls per signed wallet, which does not help an agent choose the tool.

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.