@placraftic/mcp-server

Overview Schema Source Related Servers Discussions Admin

get_order_details

Retrieve complete order manifest by ID, including customer profile, ordered parts, slicing files, and shipping tracking.

Instructions

Retrieve complete order manifest by ID including customer profile, ordered parts, slicing files, and shipping tracking

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": {
      "orderId": "<orderId>"
    },
    "name": "get_order_details"
  }
}

Input Schema

Name	Required	Description	Default
`orderId`	Yes	Unique numeric ID of the order

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. 'Retrieve' implies a read-only lookup with no mutation, and the description discloses the returned data composition. It does not mention authentication requirements, error behavior, rate limits, or whether missing orders return empty versus error responses, leaving some behavioral gaps.

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 front-loaded sentence that efficiently communicates the action, key identifier, and returned data. Every phrase earns its place.

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?

With no output schema and no annotations, the description supplies the main return-value context by listing the manifest components. For a single-parameter lookup tool, this is largely complete, though it could mention error or permission behavior.

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?

Schema description coverage is 100%, so the single orderId parameter is already clearly documented by the schema. The description adds 'by ID' but no additional syntax, format, or constraint details beyond what the schema already 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 states a specific verb (Retrieve) and resource (complete order manifest by ID), then enumerates the key data returned: customer profile, ordered parts, slicing files, and shipping tracking. This clearly distinguishes it from sibling tools like list_orders, update_order, and cancel_order.

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 'by ID' implies the tool should be used when an order ID is known, which is useful context. However, it does not explicitly state when to use this tool versus alternatives such as list_orders or update_order, nor does it mention prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.