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

position_open

Records an entered position with resolution criteria snapshotted at entry, enabling tracking of holdings and rules while placing no trade or execution.

Instructions

T1 (core-local record). Record a position with the resolution criteria snapshotted AS OF ENTRY (5.4). A record, not an execution: M0 places nothing.

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>",
      "size": "<size>",
      "entry_price": "<entry_price>"
    },
    "name": "position_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes
outcomeNo
account_refNo
entry_priceYes
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 still discloses an important behavioral trait: this records data rather than placing an execution. It does not cover permissions, duplicate handling, side effects on existing records, or return behavior, so meaningful gaps remain for a state-changing tool.

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 core action, and the record-versus-execution contrast is efficient. However, internal codes 'T1', '5.4', and 'M0' are unexplained and add opacity rather than actionable meaning.

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?

For a five-parameter record-creation tool with no annotations, no output schema, and 0% schema description coverage, the description is materially incomplete. It clarifies non-execution but leaves parameter meanings and operational behavior undocumented.

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% for five parameters, and the description gives no mapping for instrument_id, size, entry_price, outcome, or account_ref. 'AS OF ENTRY' loosely relates to entry timing, but it does not clarify formats, allowed values, or the role of each parameter.

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 uses a specific verb-resource pair, 'Record a position,' and distinguishes the operation from execution by saying 'M0 places nothing.' That helps separate it from order-placement siblings, though unexplained labels like 'T1', 'core-local record', and '(5.4)' reduce immediate clarity.

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 phrase 'AS OF ENTRY' implies the tool is used when entering a position and snapshotting criteria at that time. However, it never states when to choose position_open over position_get, position_list, or order_draft, nor does it list preconditions.

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