The Clearing — The Lantern & Consensual Agent Lab

fingerprint_json_compiler_stylometry

Inspect syntactic JSON-AST whitespace, float precision, key ordering, and \u003c escape signatures to hypothesize runtime serialization family (compiler_runtime_heuristic) without persisting prompt text or keys.

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": {
      "json_payload": "<json_payload>"
    },
    "name": "fingerprint_json_compiler_stylometry"
  }
}

Input Schema

Name	Required	Description	Default
`json_payload`	Yes	Raw JSON request body string whose formatting/serialization AST will be fingerprinted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses a privacy constraint ('without persisting prompt text or keys'), which is useful, but omits whether the operation is read-only, what permissions are needed, how results are returned, and whether any state is retained beyond the payload.

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?

The description is a single dense sentence that front-loads the inspection targets and ends with the output hypothesis and a privacy caveat. It is efficiently sized, though the technical jargon makes it slightly harder to parse than a more structured format would.

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 one-parameter forensic tool with no output schema and no annotations, the description should explain the return value (e.g., what the hypothesis looks like, confidence, or structure). It also lacks any safety or operational details. It covers the 'what' but leaves the agent without a complete picture of the call's output or behavior.

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 single parameter is fully documented in the schema. The description adds no additional meaning about the json_payload parameter beyond what the schema already provides; baseline 3 is appropriate.

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 states a specific verb ('Inspect') and enumerates the exact artifacts examined: whitespace, float precision, key ordering, and escape signatures, culminating in hypothesizing a runtime serialization family. It is clear what the tool does, though it does not explicitly differentiate itself from any sibling, which is acceptable given the unrelated catalog.

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 when-to-use guidance, no prerequisites, and no named alternatives. The purpose implies the scenario (fingerprinting JSON serialization), but the agent must infer when this tool is appropriate versus other forensic utilities.

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?