Skip to main content
Glama

Agent Exchange store

util_time

$0.001 via x402: The current time as UTC ISO 8601, unix seconds and milliseconds, the day of week and the ISO week. Pay 0.001 USDC through https://store.agentexchange.work/gw/util/time Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 burden, and it discloses the most important non-obvious behavior: this is a paid tool costing 0.001 USDC settled via x402 through a named gateway, and the schema notes that omitting x_payment returns the price instead of the answer. It stops short of covering failure modes or rate/caching behavior, but the payment/auth profile is genuinely surfaced.

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?

Compact overall, but it opens with pricing rather than purpose and repeats information: the price appears twice ('$0.001 via x402' and 'Pay 0.001 USDC') and the payment mechanism/gateway is stated redundantly. Some of that repetition could be trimmed.

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?

There is no output schema, so the description correctly enumerates the return values, and it supplies the payment context needed to actually invoke the tool. For a trivial read-only time tool this is close to complete, missing only edge-case behavior.

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 100% and the single x_payment parameter is fully documented in the schema, including the 'optional; without it the answer is the price' behavior. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 names the resource (the current time) and precisely enumerates the returned representations: UTC ISO 8601, unix seconds and milliseconds, day of week, and ISO week. This is specific enough to distinguish it from siblings like util_uuid, util_random, or util_hash, though it uses no explicit verb and never explicitly contrasts those siblings.

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?

Usage is only implied: you call it to get the time, and you must pay 0.001 USDC via x402. The payment flow is described, but there is no explicit when-to-use/when-not guidance or routing to alternatives among the many util_* siblings.

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