Skip to main content
Glama

BRAINIAC Pay, Tax & Employment Calendars

Convert a timestamp between IANA time zones

labour-tax_iana-timezone-convert
Read-onlyIdempotent

Convert an instant between IANA time zones using the runtime Intl/tzdb revision. Coordinate-to-zone lookup is not included. Price $0.01 USDC. POST /api/v1/labour-tax/iana-timezone-convert. An unpaid call returns the x402 payment terms and does not run.

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": {
      "instant": "<instant>",
      "fromTimeZone": "<fromTimeZone>",
      "toTimeZone": "<toTimeZone>"
    },
    "name": "labour-tax_iana-timezone-convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
instantYesinstant, string, length 8 to 64. Required.
toTimeZoneYestoTimeZone, string, length 1 to 64. Required.
fromTimeZoneYesfromTimeZone, string, length 1 to 64. Required.

Output Schema

NameRequiredDescriptionDefault
toNoto. Object.
fromNofrom. Object.
sourcesNosources. Array.
instantUtcNoinstantUtc. String.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds genuinely new behavioral facts: a $0.01 USDC cost, the x402 payment mechanism, and that an unpaid call returns payment terms and does not execute. That payment-gating behavior is critical for an agent to know and is nowhere in the annotations or schema.

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?

Four short sentences, front-loaded with the purpose and exclusion before the commercial/transport details. The raw endpoint string 'POST /api/v1/labour-tax/iana-timezone-convert' largely restates the tool name and is the one line that earns little.

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?

An output schema exists, so return values need not be explained, and the annotations cover the safety profile; the description fills the remaining gap with pricing and payment-gate behavior. The only meaningful omission is guidance on the accepted instant/zone string formats.

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 baseline is 3, but those schema descriptions are purely mechanical ('string, length 8 to 64') and do not reveal the expected instant format (ISO 8601 vs epoch) or the IANA zone identifier format. The description misses the chance to disambiguate the single most error-prone parameter, so no credit above baseline.

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 an instant between IANA time zones') plus the computation source ('runtime Intl/tzdb revision'), and immediately scopes out a commonly confused capability ('Coordinate-to-zone lookup is not included'). An agent can tell exactly what this does without opening the schema.

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?

The description gives a clear when-to-use context (converting an instant between two IANA zones) and one explicit exclusion (no coordinate-to-zone resolution), which functions as when-not-to-use guidance. It does not spell out a calling prerequisite sequence before payment, but there is no comparable sibling tool to route away from, so this is nearly complete.

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