Skip to main content
Glama
Sign In
Public.com MCP Server

Public.com MCP Server

Official
by PublicDotCom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_order

Read-only

Retrieve the status, fills, timestamps, and market session details for a specific Public.com order using its UUID.

Instructions

Get the status and details of a specific order, including its fills.

Returns the order with trades (each fill's tradeId, quantity, price, side, timestamp and, when reported, marketIdentificationCode — the ISO 10383 MIC of the execution venue, e.g. XNAS), filledAt, replacedAt, lastModified and equityMarketSession. equityMarketSession reports the session as REGULAR, REST_OF_DAY or TWENTY_FOUR_HOURS.

Only orders created within the last 30 days can be looked up; older orders return a not-found error. Order placement is asynchronous, so this may also return an error for an order that was just placed and has not yet been indexed.

An order that belongs to a bracket carries a bracketId — the order ID of the bracket's entry order. Pass that ID to get_orders to find the sibling legs.

Args: order_id: The UUID of the order to look up. account_id: Account ID. Optional if PUBLIC_COM_ACCOUNT_ID is set.

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": {
      "order_id": "<order_id>"
    },
    "name": "get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes
account_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag readOnly/openWorld/non-destructive, and the description adds real behavioral context beyond them: the 30-day retention window with a not-found error, the async indexing failure mode, and the exact response shape including equityMarketSession enum values and MIC semantics.

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?

Front-loaded with the core purpose and well organized in short paragraphs, but the detailed enumeration of return fields (tradeId, quantity, price, side, timestamp, MIC explanation) partly duplicates the output schema and lengthens the definition.

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?

Given two params, an output schema, and read-only annotations, everything an agent needs is present: lookup limits, error conditions, bracket handling, and optional-account behavior. No material gaps.

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?

Schema coverage is 0%, so the Args section carries the burden: order_id is documented as a UUID and account_id as optional when PUBLIC_COM_ACCOUNT_ID is set. That resolves the key ambiguity (when account_id can be omitted), though identifier format/validation detail is modest.

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?

States a specific verb and resource (get status/details of a specific order, including fills) and implicitly distinguishes itself from the plural get_orders / search_orders siblings by emphasizing one order via its UUID. The bracketId note further clarifies the single-order scope.

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

Usage Guidelines4/5

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

Gives concrete usage context: only orders from the last 30 days are retrievable, and just-placed orders may not yet be indexed due to async placement. It also routes the agent to get_orders for bracket sibling legs. No explicit exclusion versus search_orders, so not a 5.

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

Deploy Server

Other Tools