Skip to main content
Glama
Emenowicz

Hybris MCP Server

by Emenowicz

get_category

Retrieve category details from SAP Commerce Cloud using a category code to access product classification information for management tasks.

Instructions

Get details about a specific category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryCodeYesThe category code

Implementation Reference

  • The handler logic for the 'get_category' tool within the main CallToolRequestSchema dispatcher switch statement. It validates the required 'categoryCode' input and delegates to hybrisClient.getCategory.
    case 'get_category':
      result = await hybrisClient.getCategory(
        validateString(args, 'categoryCode', true)
      );
      break;
  • src/index.ts:148-161 (registration)
    Tool registration entry in the 'tools' array, used by ListToolsRequestSchema handler. Defines the tool name, description, and input schema for MCP tool discovery.
    {
      name: 'get_category',
      description: 'Get details about a specific category',
      inputSchema: {
        type: 'object',
        properties: {
          categoryCode: {
            type: 'string',
            description: 'The category code',
          },
        },
        required: ['categoryCode'],
      },
    },
  • Input schema definition for the 'get_category' tool, specifying the required 'categoryCode' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        categoryCode: {
          type: 'string',
          description: 'The category code',
        },
      },
      required: ['categoryCode'],
    },
  • Supporting method in HybrisClient that performs the actual REST API request to fetch category details using the OCC endpoints.
    async getCategory(categoryCode: string): Promise<Category> {
      return this.request<Category>(
        `/rest/v2/${encodeURIComponent(this.config.baseSiteId!)}/catalogs/${encodeURIComponent(this.config.catalogId!)}/${encodeURIComponent(this.config.catalogVersion!)}/categories/${encodeURIComponent(categoryCode)}`
      );
    }
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 of behavioral disclosure. It states the tool retrieves details, implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns structured data, or handles errors. For a tool with no annotations, this leaves significant 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, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with no wasted information, making it easy to parse quickly.

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 tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It doesn't clarify what 'details' include, how it differs from similar tools, or behavioral aspects like error handling. For a tool in a context with many sibling tools, more guidance is needed to ensure correct usage.

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 parameter semantics beyond what the input schema provides. The schema has 100% description coverage, with 'categoryCode' documented as 'The category code', so the baseline is 3. The tool description doesn't explain what a category code is, its format, or examples, offering no additional value over the 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 states the tool's purpose as retrieving details for a specific category, which is clear but vague. It uses the verb 'Get' and resource 'category', but doesn't specify what details are included or how it differs from sibling tools like 'get_categories' or 'get_product'. The purpose is understandable but lacks specificity.

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, exclusions, or compare it to sibling tools like 'get_categories' (which might list multiple categories) or 'search_products' (which might involve categories). Usage is implied only by the tool name, with no explicit context provided.

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/Emenowicz/hybris-mcp'

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