Skip to main content
Glama
shoper-mcp

shoper-mcp

by exelmedia

Drzewo kategorii / Category tree

category_tree
Read-onlyIdempotent

Retrieve category hierarchy with names and product counts, optionally from a given node and up to a set depth, to browse a Shoper store catalog.

Instructions

PL: Hierarchia kategorii z nazwami i liczbą produktów (maks. 1000 węzłów). Opcjonalnie od wybranego węzła i do zadanej głębokości. EN: Category hierarchy with names and product counts, optionally from a given node and up to a depth.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "category_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
root_idNoPokaż tylko poddrzewo od tej kategorii / subtree root id
max_depthNoMaksymalna głębokość / max depth

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive and open-world behavior, so the bar is low. The description adds a genuinely useful behavioral fact — a hard 1000-node cap — but does not say what happens when the tree exceeds it (truncation? error?) or how results are ordered.

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?

Two short bilingual sentences, front-loaded with the resource and output contents, then the optional scoping. The PL/EN duplication is presumably intentional for localization and adds little waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with full annotations and no output schema, the description covers the essentials (contents, depth, node cap). It still leaves aggregation semantics and truncation behavior unstated, which matters for an agent interpreting the returned counts.

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 both parameters are already documented in the schema and the description only restates 'from a given node / up to a depth'. No extra meaning such as whether product counts aggregate over the whole subtree or only direct children.

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?

States a specific resource (category hierarchy) plus the payload it returns (names and product counts) and a scope cap (max 1000 nodes). It is clearly distinguishable from flat listing siblings by the 'hierarchy' framing, though it never names an alternative.

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 only hints at scoped use via 'optionally from a given node and up to a depth'; it never says when to choose this over list_categories or when a full-tree walk is the wrong call. No prerequisites or exclusions are given.

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