Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-iso-to-unix

ISO To Unix: Convert iso to unix. 🆓 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-iso-to-unix"
  }
}

Input Schema

NameRequiredDescriptionDefault
isoNo
dateNo
inputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / date / description
      Removed value: -"Date to process"
    • removedInput schema / properties / input / description
      Removed value: -"Input to process"
    • removedInput schema / properties / iso / description
      Removed value: -"Iso to process"
  2. First observed

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the pay-per-call/trial constraint, which is genuinely useful, but says nothing about return format, unit of the timestamp, timezone or error behavior for malformed input.

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?

It is short and front-loaded with the conversion direction, so nothing is buried. However, half the text is a trial/pricing banner with an emoji that does not help the agent decide or invoke correctly.

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 tool with zero annotations, no output schema, and three undocumented ambiguous parameters, the description should explain input format, output unit and parameter precedence. It supplies none of these, leaving a caller with an essentially guess-driven invocation.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters (iso, date, input), none required, and the description adds no meaning whatsoever. It does not explain which of the three overlapping parameters is authoritative or how they interact, leaving an agent unable to decide how to call the tool.

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?

The description states a conversion direction (ISO to Unix), which gives a rough verb+resource. But 'ISO' is ambiguous in this ecosystem — the sibling list contains ISO week, ISO duration, ISO currency and ISO country tools — and it never says whether the output is seconds or milliseconds. It also fails to distinguish itself from close siblings like x402-date-to-unix and x402-unix-to-iso.

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 when-to-use guidance at all; the only extra sentence is a pricing note ('5 free trial calls per signed wallet'). It does not tell the agent when to pick this over x402-date-to-unix or x402-iso-week, nor what format the input must be in.

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.