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_get

Fetch a recorded position by its ID from the book's ledger of record. Use it to retrieve specific position details for reconciliation or audit.

Instructions

T0/T1. One recorded position by id.

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": {
      "position_id": "<position_id>"
    },
    "name": "position_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
position_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does not meet it. It never states that this is a read-only operation, what happens when the id is unknown (error vs empty), what fields come back, or what "T0/T1" signifies in this domain.

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?

Extremely short and front-loaded, with no padding sentences. However, brevity here comes at the cost of clarity: the cryptic "T0/T1" prefix consumes the most prominent position without conveying anything actionable.

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 simple one-parameter read tool this could be adequate, but with no annotations and no output schema the description is the only source of truth and it omits safety profile, return shape, and error semantics. It falls short of what an agent needs to invoke it confidently.

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 0% for the single required parameter. "by id" weakly ties position_id to an identifier role, but gives no format, provenance, or example, so an agent cannot tell whether an id from position_open, position_list, or an external system is acceptable.

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

Purpose3/5

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

"One recorded position by id" names the resource (a position record) and its cardinality (one), which implicitly contrasts with position_list. But there is no explicit verb, and the leading token "T0/T1" is unexplained jargon that does not help an agent understand what the tool returns.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. The singular framing hints that this is the id-based lookup as opposed to position_list or position_open, but the agent must infer that from sibling names rather than from anything the description states.

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