Skip to main content
Glama
Sign In
Carbon Copy MCP Server

Carbon Copy MCP Server

Official
by usehoplite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Order

get_order
Read-only

Retrieve details for a specific copy-trade order by ID. Check status, amounts, and order information.

Instructions

Retrieve details about a specific copy-trade order 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": {
      "id": "<id>"
    },
    "name": "get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe order ID to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the context that this is a copy-trade order, but it does not describe return format, error behavior, or any other behavioral traits. No contradiction with annotations.

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

Conciseness5/5

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

The description is a single, well-structured sentence that directly states the tool's purpose with no fluff or redundant information.

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

Completeness4/5

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

For a simple single-ID retrieval tool, the description plus annotations adequately convey the core function. However, it lacks any detail about the return value and does not reference related tools (e.g., list_orders), which would enhance completeness.

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

Parameters3/5

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

The input schema has 100% coverage for the single id parameter, already describing it as 'The order ID to retrieve.' The description reinforces 'by ID' but adds no additional semantics beyond what the schema provides.

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

Purpose5/5

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

The description uses a specific verb 'Retrieve' and clearly identifies the resource as 'details about a specific copy-trade order by ID'. The 'by ID' qualifier distinguishes this from sibling list_orders, which would list orders.

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?

The description provides no explicit guidance on when to use this tool versus alternatives like list_orders. Usage is only implied by the tool's name and ID parameter, with no mention of cases where list_orders would be more appropriate.

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