Skip to main content
Glama

unix-milestone

Unix epoch milestones. No input: the current unix seconds, and the next 100 million, 500 million, and 1 billion second marks with ISO dates and day and hour countdowns, answered fresh on every call. Price: $0.005 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "unix-milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that the tool takes no input, returns fresh data on every call, costs $0.005 per call in USDC on Base mainnet via x402, and that unpaid calls return HTTP 402 with machine-readable payment terms. It does not describe rate limits or idempotency, but for a simple read-only milestone tool the key behavioral traits are covered.

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 description is front-loaded with the core purpose and then adds output details, freshness, and payment terms without excessive wording. The opening fragment 'Unix epoch milestones.' is terse but effective, and the remaining sentence is dense yet organized.

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?

For a zero-parameter tool with no output schema and no annotations, the description is complete enough: it explains what is returned, that no input is needed, that results are fresh per call, and the payment model including the HTTP 402 behavior. An agent has everything needed to decide whether and how to call it.

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?

The tool has zero parameters, so the baseline is 4. The description reinforces this by explicitly stating 'No input,' which is consistent with the empty input 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 clearly states the resource and output: current Unix seconds plus upcoming 100M, 500M, and 1B second milestones with ISO dates and countdowns. It does not explicitly differentiate itself from sibling time-related tools such as agent-time, but the milestone focus is specific enough for an agent to understand the tool's purpose.

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?

The description implies usage by stating 'No input' and that results are answered fresh on every call, which helps an agent know how to invoke it. However, it gives no explicit when-to-use guidance or comparison to alternatives like agent-time, leaving selection context to inference.

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