ScorpTech x402 API

Timezone Convert

timezone_convert

Read-onlyIdempotent

Convert a time between IANA time zones with DST awareness: local time, UTC offset, abbreviation and DST flag on both sides, the offset difference and day shift, and each zone's next DST/offset transition (when, which way, how much). Flags nonexistent (spring-forward gap) and ambiguous (fall-back) wall times. Accepts ISO 8601, HH:MM, epoch seconds/milliseconds or "now"; up to 10 target zones. Offline (PHP's bundled tz database). Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/timezone-convert

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to_zone": "<to_zone>"
    },
    "name": "timezone_convert"
  }
}

Input Schema

Name	Required	Description
`time`	No	ISO 8601 (2026-03-08T02:30:00, optional Z or +01:00), HH:MM (today), epoch seconds or milliseconds, or "now" (default)
`to_zone`	Yes	Target IANA zone, or a comma list of up to 10. Alias: to
`from_zone`	No	IANA zone the input wall time is in (default UTC); also accepts fixed offsets like +05:30. Alias: from

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only cover the read-only/idempotent safety profile; the description goes well beyond them by disclosing the returned fields, DST-edge-case behavior (nonexistent and ambiguous wall times flagged), offline tz-database execution, cost ($0.01 USDC via x402/Solana), and an alternative HTTPS endpoint. That is exactly the kind of context annotations cannot carry.

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?

Front-loaded with the core purpose and output shape, then inputs, then pricing/transport. It is dense but nearly every clause is functional; the payment and endpoint sentences are slightly tacked-on but relevant to invocation.

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, yet the description enumerates the returned fields, edge-case flags, and transition metadata, so an agent knows what comes back. For a 3-parameter read tool this fully covers what the agent needs.

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%, so the schema already documents accepted time formats, the from_zone default of UTC, fixed offsets, and the 10-zone cap. The description restates these rather than adding new syntax or edge-case semantics, so the baseline 3 applies.

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 verb and resource ('Convert a time between IANA time zones with DST awareness') and immediately scopes the exact output fields (offset, abbreviation, DST flag, next transition). No sibling tool overlaps, and the DST-awareness qualifier distinguishes it from a naive format_convert.

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 input-context guidance ('Accepts ISO 8601, HH:MM, epoch seconds/milliseconds or "now"') and a capacity limit ('up to 10 target zones'), which tells an agent when this tool fits. It does not name an alternative or an explicit when-not condition, but no sibling is close enough to require it.

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

All ScorpTech x402 API 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?