Skip to main content
Glama

The Builders Supply catalog

Browse a category

browse_category
Read-onlyIdempotent

Products of a category and of all its subcategories, alphabetically, up to 20 per page.

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": {
      "categoryId": "<categoryId>"
    },
    "name": "browse_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax results, 1-20, default 10
offsetNooffset for the next page, default 0
categoryIdYescategory id from list_categories
orderableOnlyNotrue = only items that can be ordered now

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive semantics, so the bar is lower. The description still adds real behavioral content not in the schema: subcategory products are included and results are alphabetically ordered, both of which affect what the agent will see in the response.

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?

A single sentence with no filler that front-loads the scope (category plus subcategories) before ordering and pagination details. Every element earns its place.

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?

An output schema exists, so return values need no explanation, and the description covers scope, ordering, and page size for a straightforward read tool. It is only slightly thin on how pagination should be driven and when the orderable-only filter is appropriate.

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 coverage is 100%, so each parameter (including orderableOnly and the categoryId source) is already documented, which sets the baseline at 3. The description adds only the 'up to 20 per page' ceiling, which the schema already states as the limit maximum, and says nothing about offset paging or orderableOnly.

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?

The description states a concrete resource and scope: products belonging to a category plus all its subcategories, with alphabetical ordering and a page cap. An agent can tell this is a category-driven listing rather than a keyword search, though it never names a sibling or uses an explicit verb.

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 statement of when to use this versus search_products or list_categories, and no prerequisites or exclusions. Usage is only implied by the phrase 'of a category', leaving the agent to 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