The Clearing — The Lantern & Consensual Agent Lab

query_proxy_laundering_observatory

Reads the bounded Zero-PII Protocol AO-065 telemetry summary across Certstream recon sinkholes, split-ASN lockstep proxy rings, and multi-canary laundering bursts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "query_proxy_laundering_observatory"
  }
}

Input Schema

Name	Required	Description	Default
`window_hours`	No	Lookback window between 1 and 168 hours.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Reads' and 'bounded' hint at a safe read operation, but the description does not state permissions required, whether results are aggregated or raw, rate limits, or what 'Zero-PII' implies for output handling.

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 description is a single sentence and front-loaded, but it is dense with unexplained jargon that sacrifices clarity for brevity. Every word might earn its place in a specialist context, but the structure could be improved by separating scope from signal categories.

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

Completeness2/5

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

For a no-annotation, no-output-schema tool with one optional parameter, the description does not explain what the telemetry summary contains, how results are shaped, or what 'bounded' means in practice. The jargon-heavy scope statement is not enough to guide correct invocation reliably.

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?

The schema fully documents the single 'window_hours' parameter (1–168 hours), so the baseline is 3. The description does not add any further meaning about the parameter or how it interacts with the bounded summary.

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?

The description uses a specific verb ('Reads') and identifies the resource as a 'bounded Zero-PII Protocol AO-065 telemetry summary' spanning three named signal categories. This clearly sets it apart from generic query siblings, though the heavy jargon ('Certstream recon sinkholes', 'multi-canary laundering bursts') reduces immediate comprehensibility.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description implies it is a read-only observatory query, but an agent must infer usage from the domain terms alone.

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?