Tool-Call Origin Attestation

probe

Forged-shape probe suite {framework, version, patch_state, surface, target_url} — legs dispatched at the target; $4.99 / first free per operator ever (proven wallet required)

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": {
      "framework": "<framework>",
      "version": "<version>",
      "patch_state": "<patch_state>",
      "surface": "<surface>"
    },
    "name": "probe"
  }
}

Input Schema

Name	Required	Description	Default
`wallet`	No
`surface`	Yes
`version`	Yes
`framework`	Yes
`target_url`	No
`patch_state`	Yes
`wallet_signature`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 8, 2026
- addedInput schema / properties / target_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / wallet
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / wallet_signature
```
Added value: +{
+  "type": "string"
+}
```
First observedOct 21, 2026

TDQS

C2/5.0

Behavior2/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 discloses that legs are dispatched at the target and that a proven wallet plus $4.99 fee is required, but it omits side effects, authorization expectations, scope of the probe, and what "forged-shape" actually means operationally.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single run-on sentence mixing opaque jargon, brace-delimited parameters, and pricing details. It is not front-loaded around a clear operation, and the pricing phrase competes with the functional description.

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 7-parameter tool with no annotations, no output schema, and 0% schema description coverage, this description is far too thin. It mentions cost and wallet requirements, but leaves critical behavior, parameter semantics, and result expectations unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only enumerates parameter names without explaining their formats, allowed values, or meaning. wallet_signature is never clarified, and target_url is only indirectly implied by "at the target."

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

Purpose2/5

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

The phrase "Forged-shape probe suite" is opaque jargon and does not state a clear verb-plus-resource operation. It lists input fields and pricing, but an agent cannot confidently infer what the tool actually does or how it differs from siblings like dispatch or verdict_lookup.

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 when-not-to-use conditions, and no mention of alternatives among the sibling tools. The only contextual clue is the pricing and wallet requirement, which is a precondition rather than usage guidance.

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

All Tool-Call Origin Attestation tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?