Skip to main content
Glama
Sign In
Garden Design MCP Server

Garden Design MCP Server

by zaprojektuj-ogrod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_subcategories

Returns leaf subcategories for a top-level plant category so you can obtain a valid category ID for filtering plant product searches.

Instructions

Get the leaf subcategories of a top-level plant category. Plants use a two-level tree (6 top-level → leaves); search_products's categoryId filter requires a leaf id. Architecture and ground are flat — calling this on their top-level ids returns []. Locale follows the editor session.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "parentId": "<parentId>"
    },
    "name": "get_subcategories"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentIdYesTop-level category id from get_categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.9.3

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it explains the tree shape, that flat categories yield an empty array rather than an error, and that locale follows the editor session. It stops short of describing the returned leaf object's fields or behavior for an invalid/nonexistent id.

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?

Three tight sentences, front-loaded with purpose before the structural and locale caveats. All content earns its place, though the locale note is slightly tangential to the core selection decision.

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

Completeness4/5

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

For a one-parameter, read-only lookup with no output schema or annotations, the description covers the tree model, the usage path, and the notable empty-result case. A brief note on what a returned leaf contains would make it fully self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already says parentId is a 'Top-level category id from get_categories'. The description still adds meaning by emphasizing 'top-level' (not leaf) and warning which top-level ids are dead ends.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the leaf subcategories of a top-level plant category') and describes the underlying two-level tree (6 top-level → leaves). This clearly separates it from the sibling get_categories, which supplies the top-level ids.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the downstream use case ('search_products's categoryId filter requires a leaf id') and the failure condition ('Architecture and ground are flat — calling this on their top-level ids returns []'). The alternative source of ids, get_categories, is named in the schema and implied by the parentId description.

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

Deploy Server

Other Tools