Skip to main content
Glama

Time Zone Lookup Payment Quote

time_zone_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/time/zone (base $0.002; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?tz=America/New_York (optional to=Europe/Paris and at=2026-11-15T14:00:00Z). Time zone lookup for one IANA zone (e.g. America/New_York): local date and time, UTC offset, abbreviation, whether daylight saving is in effect and the next offset change, for now or a given instant; add to= to convert the same instant into a second zone. Computed from the IANA tz database (public domain); not an official time signal. Bad input: not charged. USDC on Base only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses the price ($0.002), the payment rail (USDC on Base only), the 402/x402 v2 protocol and GET query form, and the crucial billing behavior 'Bad input: not charged.' It also explicitly states the tool never executes the underlying check or pays, which prevents a serious misuse mode. This is rich behavioral context the structured fields cannot convey.

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?

The content is useful but poorly ordered: pricing, payment protocol and the URL appear before the reader learns what the tool does. 'USDC on Base only' is stated twice, and the nested parentheticals ('base $0.002; USDC on Base only' / '(optional to=... and at=...)') make it dense to parse. It is not bloated with filler, but it could be restructured into purpose-first, then payment, then parameters.

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?

With no output schema and a non-trivial domain, the description enumerates the returned fields and the caveat that it derives from the IANA tz database and is not an official time signal, plus the no-charge-on-bad-input rule. The gap is the shape of the paid response and whether tz is strictly required versus inferred from the example. For a quote endpoint of this complexity, it is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is an empty object with zero declared properties, so the description carries the entire burden and does so: it identifies tz as the driving parameter with a concrete example, marks to= and at= as optional, and shows the expected formats (IANA zone name, ISO-8601 instant). It adds meaning the schema provides none of.

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 names the resource (an IANA time zone lookup) and enumerates the returned fields precisely: local date and time, UTC offset, abbreviation, DST status and next offset change, plus an optional second-zone conversion. It also carves out the tool's role as a quote-only surface ('this tool never runs the check or pays'), which separates it from the paid endpoint. It falls short of 5 because the actual purpose statement is buried behind payment boilerplate rather than front-loaded.

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 through the pricing/payment instructions and the example query string, which makes clear this tool only yields terms and that payment happens over HTTP with x402 v2. However, there is no explicit statement of when to call this versus the 'http' sibling or any other quote tool, and no prerequisites are spelled out. A reader infers the workflow rather than being told it.

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.