Skip to main content
Glama
Pit Officer

Pit Officer

Official

submit_order

Submit an order intent through pre-trade checks, record the pre-trade lock, and return an approval envelope before the order is sent.

Instructions

Submit an order intent through pre-trade and obtain an approval envelope. Mutates engine state and records the pre-trade lock; protected and disabled by default.

Input Schema

NameRequiredDescriptionDefault
idNoOptional caller-supplied unique order id; omit to have the server generate one
modeYesRequired: immediate commits and settles at the order price and requires price, hold waits for execution reports
sideYesbuy or sell
priceNoLimit price as an exact decimal string; required for immediate, omit for a market order in hold
accountYesAccount code
baseAssetYesAsset being bought or sold
amountKindYesquantity or volume
quoteAssetYesAsset used for pricing
amountValueYesOrder size as an exact decimal string
missingAccountYesRequired: create or reject; for an account that does not exist yet, create is refused for an agent with loosening_refused, and reject fails the submit instead

Output Schema

NameRequiredDescriptionDefault
idYes
keyIdYes
reasonsNo
verdictYes
signedApprovalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.3/5.0
Behavior5/5

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

Since no annotations are provided, the description must carry the burden. It successfully discloses critical behavioral traits: that it 'Mutates engine state' and that it is 'protected and disabled by default.' This high-value operational context is not in the schema or annotations.

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?

The description is maximally concise, with both sentences adding unique, vital information about the tool's function and operational constraints. It is well-front-loaded.

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

Completeness5/5

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

Despite having 10 parameters and no output schema, the description is comprehensive regarding the nature of the call—it identifies the workflow, the operational state, and the risk profile (pre-trade lock/mutation). This provides a complete enough picture for an agent to decide when and if to invoke it.

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?

The schema coverage is 100%, establishing a baseline of 3. The description does not add specific meaning to any parameters, only to the overall operation, which is sufficient given the structured detail.

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

Purpose5/5

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

The description clearly defines the action (submit order intent) and the specific process involved (pre-trade and obtaining an approval envelope). This specific focus differentiates it from standard submission tools like send_live_order.

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?

While it defines its operational status ('protected and disabled by default'), it does not explicitly state when this tool should be chosen over similar submission siblings, which remains an implied context rather than an explicit rule.

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