Skip to main content
Glama

Browse a category

browse_category
Read-only

Best-selling products in one category (slug from list_categories).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryYes
currencyNoAlso show prices in this currency (USD, EUR, GBP, RUB); approximate, at today's rate. Payment is in EGP. Default EGP only.
languageNoLanguage of the answer: en, ar, ru, it or de. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / currency
      Added value: +{
      +  "description": "Also show prices in this currency (USD, EUR, GBP, RUB); approximate, at today's rate. Payment is in EGP. Default EGP only.",
      +  "enum": [
      +    "USD",
      +    "EUR",
      +    "EGP",
      +    "RUB",
      +    "GBP"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are ranked as best-sellers, but omits the default result count, whether results are paginated or truncated by 'limit', and behavior for unknown categories.

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?

A single front-loaded sentence with no filler, and the key constraint is placed directly after the purpose. It is terse to the point of leaving some behavior unstated, but nothing is wasted.

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 read-only browse tool with no output schema, the definition covers the essential call path. The remaining gaps, default limit and handling of unknown slugs, matter for correct invocation but are modest in this context.

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 50%: currency and language are documented in-schema, while category and limit are not. The description compensates for category by specifying it takes a slug from list_categories, but leaves 'limit' (min 1, max 30) without any default or effect explanation.

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 and ordering: best-selling products within a single category. The parenthetical adds a concrete input constraint (category slug comes from list_categories), which distinguishes it from a general search.

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

Usage Guidelines3/5

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

Implies a workflow prerequisite by telling the agent to obtain the slug from list_categories, which is genuinely useful routing. It does not, however, say when to prefer this over search_products or current_deals, nor what happens with an invalid slug.

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