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_get

Retrieve a single order record with lifecycle, fill, and fee reconciliation fields for auditing or ledger checks.

Instructions

T0/T1. One Order record with lifecycle + fills + fee reconciliation fields.

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": "order_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions returned fields (lifecycle, fills, fee reconciliation) but omits read-only status, authentication needs, error behavior, and confirmation that it returns exactly one record.

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 mostly front-loaded, but 'T0/T1' is unexplained internal shorthand and the sentence lacks useful structure. The remaining words do earn their place.

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 single-record lookup with no output schema, the description should explain the return shape and usage context more fully. It hints at return fields but leaves the parameter format and when-to-use gaps unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter order_id has 0% schema description coverage, and the description does not state its format, source, or an example. It adds no meaning beyond the bare schema.

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?

The description identifies the resource ('One Order record') and lists some returned fields, so the core purpose is inferable. However, it does not use an explicit retrieval verb, does not differentiate from order_draft or receipt_list, and leaves 'T0/T1' unexplained.

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?

There is no when-to-use guidance and no alternative tool is named. An agent cannot tell from the description whether order_get is the right choice versus order_draft or receipt_list.

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