Skip to main content
Glama

get_category

Retrieve category details from SAP Commerce Cloud using a category code to access product classifications and structure.

Instructions

Get details about a specific category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryCodeYesThe category code

Implementation Reference

  • The handler logic for 'get_category' in the Hybris client. It performs an API request to the OCC v2 endpoint to retrieve category details.
    async getCategory(categoryCode: string): Promise<Category> {
      return this.request<Category>(
        `/occ/v2/${encodeURIComponent(this.config.baseSiteId!)}/categories/${encodeURIComponent(categoryCode)}`
      );
    }
  • src/index.ts:149-161 (registration)
    Registration of the 'get_category' tool schema.
      name: 'get_category',
      description: 'Get details about a specific category',
      inputSchema: {
        type: 'object',
        properties: {
          categoryCode: {
            type: 'string',
            description: 'The category code',
          },
        },
        required: ['categoryCode'],
      },
    },
  • The tool call handler switch case that invokes the 'getCategory' method from the Hybris client.
    case 'get_category':
      result = await hybrisClient.getCategory(
        validateString(args, 'categoryCode', 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 of behavioral disclosure. It states the tool 'Get details,' implying a read-only operation, but doesn't address permissions, rate limits, error handling, or what 'details' includes (e.g., fields, format). This leaves significant gaps for a tool with no annotation coverage.

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

Conciseness4/5

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

The description is a single, efficient sentence ('Get details about a specific category') that is front-loaded and wastes no words. It could be more structured by including key details, but it's appropriately sized for its limited content, earning a high score for conciseness.

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 explain what 'details' are returned, how errors are handled, or differentiate from siblings. For a read operation with no structured output, more context is needed to guide effective 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?

The input schema has 100% description coverage, with 'categoryCode' documented as 'The category code.' The description adds no additional meaning beyond this, as it doesn't explain the parameter's role, format, or examples. With high schema coverage, the baseline is 3, and the description doesn't compensate or add value.

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 ('Get details about a specific category'), which is clear but vague. It specifies the verb ('Get') and resource ('category'), but doesn't differentiate from sibling tools like 'get_categories' or explain what 'details' entail. It avoids tautology but lacks specificity about scope or content.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_categories' (which might list categories) or 'get_product' (which might relate to categories), nor does it specify prerequisites or exclusions. The description implies usage for retrieving category details but offers no contextual direction.

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