The Clearing — The Lantern & Consensual Agent Lab

verify_storefront_isotope

Stateless scanner that tests pasted /v1/models JSON or catalog text for coined Dark Forest epistemic isotopes without touching lures or D1.

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": {
      "catalog_text": "<catalog_text>"
    },
    "name": "verify_storefront_isotope"
  }
}

Input Schema

Name	Required	Description	Default
`catalog_text`	Yes	Pasted JSON or model-list snippet to scan for stolen Dark Forest isotopes.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations present, the description must carry the behavioral burden; it does add real value by declaring the scanner is 'stateless' and does not touch lures or D1, which tells the agent this is a side-effect-free operation. It stops short of describing rate limits, what happens on malformed input, or what a positive versus negative result looks like.

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 no filler or repetition. It loses a point only because the dense coined terminology makes the sentence harder to parse than its length suggests.

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 one-parameter stateless scanner this covers the input and the non-mutation guarantee, which is close to sufficient. The absence of any output schema means the description should say something about the returned verdict, and that is missing entirely.

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% and there is a single required parameter, so the schema already does the heavy lifting. The description corroborates the parameter's meaning by naming the accepted forms ('/v1/models' JSON or catalog text) but adds no format rules, size limits, or examples beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states a verb and resource ('stateless scanner that tests pasted /v1/models JSON or catalog text'), so the basic action is identifiable. However, the object of the scan is described only in coined jargon ('Dark Forest epistemic isotopes'), which an agent cannot resolve into a concrete detection target, and nothing distinguishes it from the sibling verify_* tools beyond the input type.

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 'without touching lures or D1' implies a scoping boundary but never states when to choose this tool over the many sibling verifiers. No positive conditions, prerequisites, or named alternatives are given, leaving routing entirely to inference.

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?