Pit Officer

Official

Overview Schema Source Related Servers Discussions Admin

submit_drop_copy_order

Submits a drop-copy order through the policy pipeline, ignoring policy rejects and kill-switch blocks to record an already-executed trade while policies update state.

Instructions

Submit a drop-copy order through the normal policy pipeline while ignoring policy rejects and existing account or group kill-switch blocks. Policies retain their normal state changes. The id is optional; when omitted, the store assigns it. No lifecycle event is signed. Mutates engine state; protected and disabled by default.

Input Schema

Name	Required	Description
`id`	No	Optional caller-supplied unique order id; omit to have the store assign one
`side`	Yes	buy or sell
`price`	No	Required limit price as an exact decimal string; market orders are rejected for drop-copy
`account`	Yes	Account code
`baseAsset`	Yes	Asset being bought or sold
`amountKind`	Yes	quantity or volume
`quoteAsset`	Yes	Asset used for pricing
`amountValue`	Yes	Order size as an exact decimal string
`missingAccount`	Yes	Required: must be create, as a drop-copy reports an execution that already happened and cannot reject an account that does not exist yet; for such an account, create is refused for an agent with loosening_refused

Output Schema

Name	Required	Description	Default
`id`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Nov 2, 2026

TDQS

A4/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the bypass of policy rejects and account/group kill-switches, that policy state changes still apply, that no lifecycle event is signed, that engine state is mutated, and that it is protected/disabled by default. These are exactly the traits an agent must know before invoking a dangerous write.

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

Conciseness5/5

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

Five short sentences, front-loaded with the core action and the most consequential behavior (ignoring rejects/kill-switches), then the id default, signing, and gating. Nothing is padding.

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

Completeness4/5

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

An output schema exists and the input schema is fully described, so the description needn't explain returns or field formats. It covers the safety/gating profile well; only the enablement path for a 'protected and disabled by default' tool is left unstated.

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 coverage is 100%, so the schema already documents all nine parameters including the id and missingAccount quirks. The description only restates that id is optional, adding no syntax or format detail beyond the structured fields, so baseline 3 applies.

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?

Specific verb ('Submit') plus a distinct resource ('drop-copy order') and a precise qualifier about the policy pipeline. It does not name the sibling it supersedes (submit_order / send_live_order), but the drop-copy framing plus the bypass semantics makes it functionally distinguishable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The use case is implied by the drop-copy concept and by 'protected and disabled by default', but there is no explicit statement of when to choose this over submit_order or send_live_order, nor any prerequisite/enablement steps. An agent must infer the selection rule.

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

Deploy Server