Agent Decoy Gateway

Overview Schema Source Related Servers Discussions Admin

lookup_settlement_reference

Opens a synthetic settlement-reference trail inside an isolated security lab, letting authorized agents exercise a bounded lookup workflow for controlled experiments.

Instructions

Open a synthetic settlement-reference trail in an isolated security lab.

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": "lookup_settlement_reference"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`kind`	Yes
`handle`	Yes
`message`	No
`terminal`	Yes
`reference`	Yes
`steps_used`	Yes
`steps_remaining`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

C2.9/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. "Isolated security lab" and "synthetic" weakly signal a sandboxed, non-production, non-destructive action, which is useful, but it never states whether a persistent object is created, whether state is shared with the follow tool, or whether auth is required.

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 verb first and no redundant padding. The trailing qualifier "in an isolated security lab" is doing real work (signalling sandbox behavior) even if the phrasing is unusual.

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?

A zero-parameter tool with an output schema is a low-complexity case, and the description covers the basics plus a sandbox hint. Still missing is the link to its sibling and any statement of what state the call establishes, which matters because the follow tool likely depends on it.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not misrepresent any inputs.

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?

The verb+resource pair ("Open ... settlement-reference trail") is identifiable, and "open" versus the sibling's "follow" hints at creating vs continuing a trail. However, "synthetic settlement-reference trail in an isolated security lab" is cryptic about what is actually opened or what domain object is touched, so an agent gets only a vague sense of purpose.

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?

No when-to-use condition, prerequisite, or exclusion is given. The sibling follow_settlement_reference is a natural alternative (start a trail vs continue one) but the description never mentions it or any selection rule, leaving the agent to guess which to call.

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

Deploy Server