Skip to main content
Glama
Sign In
Cyan Eclipse Book MCP

Cyan Eclipse Book MCP

Official
by CYAN-ECLIPSE-TECHNOLOGIES-LLC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

order_draft

Build an unsubmitted MARKET or LIMIT order draft with a receipt for pre-evaluation; it does not submit orders and returns NOT_EVALUATED_M0_DATA_ONLY.

Instructions

T1. Build an UNSUBMITTED Order in DRAFT (MARKET|LIMIT only) with its receipt. M0 has no submission path at any tier; mandate pre-evaluation reads NOT_EVALUATED_M0_DATA_ONLY (spec 5.6, 7.2).

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": {
      "instrument_id": "<instrument_id>",
      "side": "<side>",
      "size": "<size>"
    },
    "name": "order_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
sizeYes
typeNo
limit_priceNo
instrument_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that the order is UNSUBMITTED and remains in DRAFT, that only MARKET and LIMIT are allowed, and that pre-evaluation reads NOT_EVALUATED_M0_DATA_ONLY. It does not cover permissions, persistence, validation behavior, or side effects beyond the no-submission constraint.

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?

The description is short and front-loads the draft-order purpose. However, the T1/M0 shorthand and spec references make it denser and more cryptic than necessary for an agent that may not know the internal notation.

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

Completeness2/5

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

There is no output schema, no annotations, and 0% schema description coverage across five parameters. The description gives useful high-level constraints but is not complete enough to explain the required inputs or the receipt output for a draft-order creation tool.

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 description coverage is 0%, so the description should compensate for five undocumented parameters. It only indirectly specifies type as MARKET|LIMIT and implies a receipt, while side, size, instrument_id, and limit_price receive no semantic explanation. This leaves most parameter meaning to inference.

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?

The description states a specific verb and resource: build an unsubmitted order in DRAFT with its receipt. It narrows the order types to MARKET|LIMIT and explicitly separates this from a submission path, which helps distinguish it from order_get. The T1/M0 shorthand is cryptic but the core purpose is clear.

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?

It provides an important usage constraint: M0 has no submission path at any tier, so this tool cannot submit an order. It also states the mandate pre-evaluation status, but it does not explicitly name alternatives or say when to use order_draft versus sibling tools like order_get.

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