QuickBuild token-saver tools + x402

util_time

Read-onlyIdempotent

[PAID $0.005 USDC per call via x402 on Base; errors are free] Authoritative current time from the Cloudflare edge clock. Optional tz (IANA name, e.g. Asia/Saigon, default UTC). Unknown timezone = 400, never charged.

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

Name	Required	Description	Default
`tz`	No	IANA timezone (default UTC)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavioral traits: pricing ($0.005 USDC per call via x402 on Base), free errors, an authoritative edge-clock source, and the 400-never-charged behavior for unknown timezones.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the paid-call notice, then immediately states the tool's purpose and key parameter behavior. No sentence 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 one-parameter utility with no output schema, the description covers purpose, pricing, timezone handling, and error behavior. It could optionally mention the returned time format, but the essential information is present.

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?

Schema coverage is already 100%, but the description adds useful semantics: an IANA example (Asia/Saigon), the UTC default, and the error behavior for unknown timezones. It stops short of describing accepted casing or edge cases.

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?

The description states a specific resource and source: 'Authoritative current time from the Cloudflare edge clock.' It is clearly distinguishable from unrelated sibling utilities such as util_random, util_uuid, and util_hash.

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 implied: call this when an authoritative current time is needed. It does not explicitly state when not to use it or name alternatives, but the tool's scope is simple enough that little routing guidance is required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All QuickBuild token-saver tools + x402 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?