Skip to main content
Glama

get_order

Retrieve specific order details from SAP Commerce Cloud using user ID and order code to track purchases and manage customer transactions.

Instructions

Get details of a specific order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesUser ID or email
orderCodeYesOrder code/number

Implementation Reference

  • The implementation of the getOrder tool, which performs an API request to fetch order details.
    async getOrder(userId: string, orderCode: string): Promise<Order> {
      return this.request<Order>(
        `/occ/v2/${encodeURIComponent(this.config.baseSiteId!)}/users/${encodeURIComponent(userId)}/orders/${encodeURIComponent(orderCode)}?fields=FULL`
      );
    }
  • src/index.ts:177-193 (registration)
    Tool definition and registration for 'get_order' in the MCP server index.
      name: 'get_order',
      description: 'Get details of a specific order',
      inputSchema: {
        type: 'object',
        properties: {
          userId: {
            type: 'string',
            description: 'User ID or email',
          },
          orderCode: {
            type: 'string',
            description: 'Order code/number',
          },
        },
        required: ['userId', 'orderCode'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic action. It doesn't reveal whether this is a read-only operation, if it requires authentication, what happens with invalid inputs, or the format of returned details, leaving significant gaps in understanding the tool's behavior.

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 extremely concise—a single sentence that directly states the tool's purpose without any fluff. It's front-loaded and wastes no words, making it efficient for an agent to parse, though this brevity contributes to gaps in other dimensions.

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?

Given the complexity of retrieving order details (which may involve permissions, error handling, or data formats) and the absence of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects, usage context, or output expectations, making it insufficient for an agent to fully understand the tool's role and limitations.

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 description adds no meaning beyond what the input schema provides, as schema description coverage is 100% with clear parameter descriptions. The baseline score of 3 reflects adequate parameter documentation solely from the schema, with the description offering no additional context about how parameters interact or their real-world significance.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('details of a specific order'), making it easy to understand what the tool does. However, it doesn't distinguish itself from sibling tools like 'get_orders' (which likely lists multiple orders) or 'get_product' (which retrieves product details), missing an opportunity for clearer differentiation.

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 guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing both userId and orderCode), compare it to 'get_orders' for listing orders, or specify contexts where this tool is appropriate, leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcieunic/hybris-mcp-main'

If you have feedback or need assistance with the MCP directory API, please join our Discord server