The Clearing — The Lantern & Consensual Agent Lab

simulate_shot_clock_budget

Audits eligibility and shot-clock timing budgets (4.5s idle vs. 12s keystroke-extended vs. hard safety bypass) for a candidate completion request.

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": {
      "prompt_text": "<prompt_text>"
    },
    "name": "simulate_shot_clock_budget"
  }
}

Input Schema

Name	Required	Description
`prompt_text`	Yes	Candidate prompt text.
`wants_stream`	No	Whether caller requested SSE streaming.
`is_gatekeeper`	No	True if binary_news_gatekeeper YES/NO.
`intercept_mode`	No	Switchboard filtering mode.
`has_airspace_signal`	No	True if AO-064 airspace safety signal.
`is_trivial_healthcheck`	No	True if machine ALPHA/math ping.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the actual decision policy — 4.5s idle, 12s keystroke-extended, hard safety bypass — which is real behavior beyond the schema, but it never states that the tool is side-effect free (only the name "simulate" implies it) or what form the audit verdict takes.

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 front-loaded sentence with the core purpose first and the timing constants in a compact parenthetical. Dense but no wasted clauses; it could only be improved by adding the missing guidance rather than by trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter audit tool with no output schema, the definition explains the input-side policy but says nothing about the return value — whether it yields a boolean verdict, remaining budget, or a reason code. That is the main unresolved question an agent would have before calling it.

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 is already documented in the schema, and the baseline is 3. The description adds conceptual framing (eligibility, timing budgets) that ties the flags together but gives no per-parameter meaning such as how wants_stream or intercept_mode shift the budget.

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 ("Audits") and a specific resource (eligibility and shot-clock timing budgets) for a candidate completion request, and even enumerates the three timing regimes it evaluates. The purpose is clear without opening the schema, though it does not explicitly contrast itself with any sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The phrase "for a candidate completion request" hints that this is a pre-flight check, but there is no explicit statement of when to call it, when not to, or what alternative to use. An agent must infer the call site entirely from the word "candidate."

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

All The Clearing — The Lantern & Consensual Agent Lab 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?