Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Today's Orders

today_orders
Read-onlyIdempotent

Retrieve all orders placed today, with optional symbol filter. For US accounts, filter by Buy/Sell action, page, and limit to paginate results.

Instructions

Get orders placed today. Returns orders[]{order_id, symbol, side, order_type, status, quantity, price, submitted_at, executed_quantity, executed_price}. Pass symbol to filter. US accounts only: us_action (Buy/Sell), us_page, us_limit filter/paginate via a separate US order endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoFilter by symbol, e.g. "700.HK". Omit to return all today's orders.
us_pageNoUS accounts only: page number (default 1).
us_limitNoUS accounts only: page size (default 20).
us_actionNoUS accounts only: filter by side, "Buy" or "Sell". Omit for all.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv0.8.4
    • addedInput schema / properties / us_action
      Added value: +{
+  "description": "US accounts only: filter by side, \"Buy\" or \"Sell\". Omit for all.",
+  "type": "string"
+}
    • addedInput schema / properties / us_limit
      Added value: +{
+  "description": "US accounts only: page size (default 20).",
+  "format": "int32",
+  "type": "integer"
+}
    • addedInput schema / properties / us_page
      Added value: +{
+  "description": "US accounts only: page number (default 1).",
+  "format": "int32",
+  "type": "integer"
+}
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"TodayOrdersParam"
  3. Addedv0.4.5
  4. Removedv0.4.0
  5. Addedv0.3.2
  6. Removedv0.3.1
  7. First observedv0.1.12

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds output structure but the confusing US account statement may mislead about actual behavior, reducing transparency.

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

Conciseness3/5

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

Relatively concise with main purpose front-loaded. However, the confusing statement about US accounts wastes space and reduces clarity.

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?

Explains output structure and symbol filtering, but lacks explanation of differentiation from 'today_executions'. The US account parameter ambiguity leaves gaps in understanding.

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 coverage is 100%, so baseline 3. Description adds meaning for 'symbol' (filter) but says US account parameters should be used via a separate endpoint, contradicting their presence in the schema and creating confusion.

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?

Clearly states 'Get orders placed today' and lists return fields, distinguishing from siblings like 'today_executions' and 'history_orders'. However, the US accounts part introduces ambiguity about whether to use this tool or a separate endpoint.

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?

Implies use for today's orders but does not explicitly state when not to use or mention alternatives. The confusing guidance on US accounts further detracts from clear usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server