Skip to main content
Glama

wait_bound

Read-onlyIdempotent

Calculates a wait's deadline from its governing clock—fleet cycle math, a named external anchor, or a CEO ladder rung—and returns the bound in seconds, UTC/local time, and a TTL integer.

Instructions

Derives a deadline from the mechanism a wait actually rides (three-clock law v1.1 A2): fleet = k x cycle_seconds + PERT(turn) + 1 sd; world = PERT(turn) with a REQUIRED named external anchor; ceo = the named ladder rung (machine time never consumes a CEO rung). Returns the bound in seconds, the deadline in UTC and local (PT by default), and an envelope-ready TTL integer. Round human hours are unexamined slack.

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": {
      "clock_class": "<clock_class>"
    },
    "name": "wait_bound"
  }
}

Input Schema

NameRequiredDescriptionDefault
ceo_rungNoCEO only REQUIRED: ladder rung (pass=15m, burst=1h, sleep=1d, cycle=1wk, season=1mo). The rung IS the bound.
cycles_kNoFleet only: cycle multiplier, 1..5 by law (more cycles = broken mechanism, not generous deadline). Default 2.
time_zoneNoIANA timezone for the rendered deadline. Default America/Los_Angeles (PT display law).
clock_classYesWhich of the three clocks this wait rides: fleet = agent-only (mechanism cycle math), world = external 1:1 (requires external_anchor), ceo = the named ladder (requires ceo_rung). Three-clock law v1.1 A2.
cycle_secondsNoFleet only: the mechanism cycle in seconds the wait rides (org bus sweep = 40). Default 40.
from_timestampNoISO 8601 start instant; omit for now.
external_anchorNoWorld only REQUIRED: the named external event this wait is bound to (1:1, no dilation).
turn_optimistic_minutesNoTurn-time PERT optimistic in minutes. Default 15.
turn_most_likely_minutesNoTurn-time PERT most-likely in minutes. Default 45.
turn_pessimistic_minutesNoTurn-time PERT pessimistic in minutes (busy/turn-driven seats). Default 120.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety and determinism are covered. The description adds genuine behavior beyond that: the returned values (bound in seconds, UTC and local deadline, TTL integer), the rule that machine time never consumes a CEO rung, and the warning that round human hours are unexamined slack. What it omits is any statement of the output's actual shape or units interaction, leaving the TTL integer and default PT rendering somewhat opaque.

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 purpose is front-loaded and there is little padding, but the prose is compressed to the point of opacity: unexplained identifiers ('v1.1 A2'), 'envelope-ready TTL integer', and the closing aphorism 'Round human hours are unexamined slack' cost the reader more than they save. A plainer sentence on what is returned and when each clock applies would earn the same space.

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 10 parameters, one required, full schema coverage, and no output schema, the description is expected to explain return values and mode requirements, and it does both: three output quantities and the per-mode prerequisites. The gaps are minor, chiefly the absence of any statement about what happens when optional PERT inputs are omitted or how the TTL relates to the bound.

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 and the schema already explains each parameter, including defaults and the 1..5 law on cycles_k. The description does add real semantic value by giving the composition formulas (fleet = k x cycle_seconds + PERT(turn) + 1 sd; world = PERT(turn) plus anchor; ceo = the rung itself), which tells the agent how parameters combine rather than what each one is. It does not explain from_timestamp behavior or the PERT weighting beyond what the schema says.

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?

States a specific verb and product: 'Derives a deadline from the mechanism a wait actually rides,' then names the three clock classes it can compute from. An agent knows this computes a time bound rather than performing time arithmetic. It does not differentiate itself from siblings like time_math or parse_duration, and the internal jargon ('three-clock law v1.1 A2', 'envelope-ready TTL') blurs rather than sharpens the purpose.

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?

Guidance is delivered through the mode rules: fleet for agent-only waits, world for external 1:1 waits requiring a named anchor, ceo for named ladder rungs. That is effectively a when-to-use decision procedure keyed to the required clock_class parameter. It stops short of naming an alternative tool or stating when not to call this at all.

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