Skip to main content
Glama

agent-time

Agent time. The current UTC instant for agents with no clock: unix seconds and milliseconds, ISO 8601 and RFC 2822 renderings, and the UTC calendar breakdown with weekday, month, day of year, ISO week, quarter, and leap year, answered fresh on every call. Price: $0.01 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": "agent-time"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses freshness (no caching), the exact price and payment rail ($0.01 USDC on Base mainnet over x402), and the failure mode of an unpaid call (HTTP 402 with machine-readable terms). That is precisely the operational detail an agent needs before invoking a paid endpoint.

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 first sentence is front-loaded and the rest is dense with no filler. The enumeration of calendar fields is somewhat long, but each item is real return-value content rather than decoration.

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?

There is no output schema, so the description must describe the return shape, and it does that field-by-field plus payment and error behavior. Nothing an agent needs to form and pay for the call correctly is missing.

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 takes no parameters, so the baseline is 4. The description correctly adds no parameter guidance and instead spends its words on return values, which is the right allocation for a zero-arg call.

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

Purpose5/5

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

States a specific resource (the current UTC instant) and enumerates the exact renderings returned (unix s/ms, ISO 8601, RFC 2822, calendar breakdown). This clearly distinguishes it from siblings like iso-week, unix-milestone, or dst-state, which are partial views of the same domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context: it is for 'agents with no clock' that need the current instant, and notes it is answered fresh on every call. It stops short of explicitly naming when not to use it or pointing at a narrower sibling, but the audience condition is unambiguous.

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