Skip to main content
Glama

Search product categories

search_categories
Read-onlyIdempotent

Find product categories covered by Intelligence Pick. Returns up to 10 names with their URLs.

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": {
      "query": "<query>"
    },
    "name": "search_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond that: a hard result cap of 10 and that each hit carries a name and URL. It stays silent on match semantics (exact vs. fuzzy), empty-result behavior, and whether results are ranked.

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 compact sentences with the capability front-loaded and the return shape second; nothing is redundant. 'Covered by Intelligence Pick' is domain jargon that slightly slows the first read but does add scoping information.

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 one-parameter read-only lookup with no output schema, the description does enough to convey the response shape (up to 10 name/URL pairs). It falls short on the two things an agent still needs: what the query string should look like and how matches are determined.

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

Parameters2/5

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

The single required parameter 'query' has zero schema description coverage, so the description carries the full burden and does not meet it. It never says what the query should contain — a category name, a keyword, a URL fragment — or how the 2-200 character constraint is interpreted.

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 verb and resource ('Find product categories') and scopes it to those 'covered by Intelligence Pick'. It does not explicitly contrast with the siblings get_brief_summary and get_pick, but the resource noun is distinct enough that an agent can tell what it retrieves.

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?

There is no guidance on when to call this versus get_pick or get_brief_summary, nor any note on prerequisites or what to do when no categories match. Usage is only implied by the verb 'Find'; an agent must infer the routing itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources