Skip to main content
Glama

get_orders

Retrieve order details for a specific user from SAP Commerce Cloud using their user ID or email address.

Instructions

Get orders for a specific user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesUser ID or email

Implementation Reference

  • Actual implementation of the getOrders tool logic in the Hybris client class.
    async getOrders(userId: string): Promise<{ orders: Order[] }> {
      return this.request<{ orders: Order[] }>(
        `/occ/v2/${encodeURIComponent(this.config.baseSiteId!)}/users/${encodeURIComponent(userId)}/orders?fields=FULL`
      );
    }
  • src/index.ts:162-175 (registration)
    Registration of the get_orders tool with its input schema.
    {
      name: 'get_orders',
      description: 'Get orders for a specific user',
      inputSchema: {
        type: 'object',
        properties: {
          userId: {
            type: 'string',
            description: 'User ID or email',
          },
        },
        required: ['userId'],
      },
    },
  • The handler case in index.ts that calls the hybrisClient for the get_orders tool.
    case 'get_orders':
      result = await hybrisClient.getOrders(
        validateString(args, 'userId', true)
      );
      break;
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 burden. It states it 'gets' orders, implying a read-only operation, but doesn't disclose behavioral traits like whether it returns all orders or is paginated, what format the output is in, error conditions, or rate limits. The description is minimal and lacks necessary context for safe invocation.

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, clear sentence with zero waste. It's front-loaded with the core purpose and efficiently conveys the essential information without unnecessary details, making it highly concise and well-structured.

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 no annotations and no output schema, the description is incomplete for a tool that likely returns complex order data. It doesn't explain what 'orders' entail (e.g., fields, format), potential side effects, or error handling. For a read operation with undocumented behavior, more context is needed to ensure reliable use.

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%, with the schema fully documenting the 'userId' parameter as 'User ID or email'. The description adds no additional meaning beyond this, as it doesn't explain parameter usage or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the schema handles parameter documentation adequately.

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 action ('Get') and resource ('orders'), and specifies the scope ('for a specific user'). It distinguishes from sibling tools like 'get_order' (singular) by implying it retrieves multiple orders. However, it doesn't explicitly differentiate from potential filtering tools like 'search_products' for 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 guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), exclusions, or compare it to siblings like 'flexible_search' or 'get_order'. Usage is implied only by the name and description, with no explicit context.

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