VALUE Verdicts

Time portal (moment card and portal minutes)

time_portal

Read-only

Reads the clock at a place and instant and returns the moment card (digit-reduced local HH:MM read as a Major Arcana number), whether this minute is a portal, and the previous and next portal minutes (mirrors, triples, ascending/descending sequences, pi 3:14, phi 6:18, and 12-hour echoes) with exact UTC instants and countdowns. Clock: civil timezone (given, or looked up from the coordinate), mean solar time, or UTC. DST-aware. Same input and "at" always give the same result, with a receipt hash. Price: $0.01 USDC per call after 25 free calls per day.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "time_portal"
  }
}

Input Schema

Name	Required	Description
`at`	No	Optional UTC instant, e.g. 2026-11-02T08:30Z. Defaults to now.
`clock`	No	Optional. civil (default), solar (mean solar time at the longitude) or utc.
`_payment`	No	x402 v2 payment: base64 PaymentPayload, as you would send in the PAYMENT-SIGNATURE header. Only needed after the free allowance is used.
`latitude`	Yes	Latitude from -90 to 90.
`longitude`	Yes	Longitude from -180 to 180.
`timezoneId`	No	Optional IANA timezone, e.g. "Africa/Cairo". If omitted, it is looked up from the coordinate (falls back to solar time).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses determinism ('same input and "at" always give the same result'), a receipt hash, DST-awareness, clock-mode behavior, and a concrete cost model ($0.01 USDC after 25 free calls). These are exactly the operational facts an agent needs before calling.

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-loads the core action and return shape, then appends clock modes, determinism, and price. The enumerated portal types are long but genuinely informative; only mildly dense as a single paragraph, with no filler sentences.

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, so the description must carry the return-value burden — and it does, naming the moment card format, the portal flag, the neighboring portal set with UTC instants and countdowns, and the receipt hash. Payment behavior is also covered, so an agent knows how to invoke it after the free allowance.

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 all six parameters are already documented in structured form. The description's clock explanation (civil/solar/utc, timezone lookup with solar fallback) essentially restates the schema descriptions rather than adding syntax or format detail, so 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?

Specific verb and resource: 'Reads the clock at a place and instant' and enumerates exactly what comes back (moment card, portal status, previous/next portal minutes with UTC instants and countdowns). No sibling tool does anything similar, so the agent can distinguish it immediately.

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?

Implies usage context clearly (you need a point-in-time read at a coordinate, with the option of now via default) and states the pricing precondition of 25 free calls/day, which affects whether to call. It does not explicitly say when NOT to use it or name an alternative, but no sibling overlaps with this capability.

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

All VALUE Verdicts 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?