Lordevo Shop (x402 website checks)

Time zone conversion (IANA zones, offsets, DST) ($0.002/call)

time_convert

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Data utilities] Converts a date-time from one IANA time zone to another, or gives the current time in a zone, with ISO 8601 output, UTC offsets, abbreviation, whether DST is in effect and the next DST change, and flags times skipped or repeated by DST. Input: to, optional from (default UTC) and datetime (default now). Offline.

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": "<to>"
    },
    "name": "time_convert"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	IANA time zone, e.g. Europe/London, America/New_York, Asia/Kuala_Lumpur or UTC
`from`	No	IANA zone the datetime is in (default UTC)
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.
`datetime`	No	ISO 8601 date/time (2026-11-01T09:30, optional Z or +08:00), Unix seconds, or now (default)

Output Schema

Name	Required	Description
`to`	No
`utc`	No
`from`	No
`tool`	No
`cache`	No
`input`	No
`notes`	No
`_trial`	No	Present when the call was a free trial call.
`provider`	No
`price_usd`	No
`unix_seconds`	No
`interpreted_as`	No
`difference_hours`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / trial / description

Previous value: -"Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms."New value: +"Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms."

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / trial

Added value: +{
+  "description": "Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "required": [
+        "tool",
+        "utc",
+        "from",
+        "to"
+      ]
+    },
+    {
+      "properties": {
+        "accepts": {
+          "type": "array"
+        },
+        "error": {
+          "type": "string"
+        },
+        "resource": {
+          "type": "object"
+        },
+        "x402Version": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "x402Version",
+        "accepts"
+      ]
+    },
+    {
+      "properties": {
+        "charged": {
+          "type": "boolean"
+        },
+        "error": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "_trial": {
+      "description": "Present when the call was a free trial call.",
+      "type": "object"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "difference_hours": {
+      "type": "number"
+    },
+    "from": {
+      "type": "object"
+    },
+    "input": {
+      "type": "object"
+    },
+    "interpreted_as": {
+      "type": "string"
+    },
+    "notes": {
+      "type": "array"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "to": {
+      "type": "object"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "unix_seconds": {
+      "type": "integer"
+    },
+    "utc": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedNov 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context the annotations cannot: the $0.002 x402/USDC-on-Base payment model, the free-trial bypass, and that DST-skipped or repeated times are explicitly flagged rather than silently coerced.

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?

A single dense paragraph with zero filler sentences, though the pricing string is front-loaded ahead of the actual purpose, which pushes the most important information to second position. Slightly better ordering would put the verb-resource clause first.

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?

Given an output schema, full parameter coverage, and rich annotations, the description supplies the remaining pieces an agent needs: zone identifier format, defaults, DST edge-case behavior, offline status, and cost. The only shortfall is the absence of routing guidance against nearest siblings like date_calc.

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 every parameter, including the 'trial' flag and the accepted datetime formats, is already documented in structured form. The description only restates 'to, optional from (default UTC) and datetime (default now)', adding no syntax or constraint beyond the schema — baseline 3.

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 names a specific verb and resource ('Converts a date-time from one IANA time zone to another') plus a second mode ('gives the current time in a zone'), and enumerates the returned fields. An agent can distinguish this from date_calc or unit_convert by the explicit IANA-zone framing 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states defaults ('from' defaults to UTC, 'datetime' defaults to now) and that the tool works offline, which implies when it applies. However, it never says when to prefer this over the sibling date_calc or unit_convert, and gives no exclusions or prerequisites beyond the zone-format name.

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

All Lordevo Shop (x402 website checks) 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?