Skip to main content
Glama

convert_epoch

Paid $0.02 (x402, USDC Base): Epoch <-> ISO-8601 time converter with UTC parts and relative age. Args: ts (unix) or iso (string).

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

Input Schema

NameRequiredDescriptionDefault
tsNo
isoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 burden, and it does disclose something genuinely useful beyond the schema: the call costs $0.02 via x402/USDC on Base. It also reveals the return contents (UTC parts, relative age). However, it is silent on validation behavior for malformed input, precedence when both fields are set, and error/payment-failure handling.

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?

A single dense sentence that front-loads the cost and then the capability, with zero filler. Structure is slightly compressed ('Args:' list inline), but nothing is wasted.

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 two-parameter utility with no output schema and no annotations, the description covers cost, directionality, accepted inputs, and the shape of the result. Minor gaps around input precedence and error cases are acceptable at this complexity.

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 0% and both properties are untyped-anonymous strings, so the description does real work by labeling ts as unix time and iso as an ISO-8601 string, plus the 'or' hinting at a one-of choice. It still omits accepted formats (seconds vs milliseconds, timezone expectations) needed to call it correctly.

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?

States a specific conversion verb with both directions ('Epoch <-> ISO-8601') and names the extra outputs (UTC parts, relative age), which is far more informative than the bare tool name. It stops short of differentiating itself from the nearby time-related sibling get_time, so an agent must still infer which to pick.

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?

'Args: ts (unix) or iso (string)' implies usage but only at the parameter level; there is no guidance on when to prefer this over get_time or get_coin_convert, and no statement of what happens if both are supplied or neither is. Usage is implied rather than directed.

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