Skip to main content
Glama

walmart: Browse a Walmart category

walmart_category
Read-only

Browse a Walmart category. Public Walmart category listing: the same shape as walmart.search, keyed by category id instead of a query. Costs 3 credits.

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": "walmart_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldNoWalmart marketplace, default com. One of: com, ca
pageNo
categoryYesWalmart category id, the last part of a category page's URL, e.g. "3944_1089430_37807". The page's URL is also accepted, on the marketplace set by `tld`.
country_codeNo
cache_max_ageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Walmart category id, e.g. \"3944_1089430_37807\""New value: +"Walmart category id, the last part of a category page's URL, e.g. \"3944_1089430_37807\". The page's URL is also accepted, on the marketplace set by `tld`."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new context: it is a public listing, it returns the same shape as walmart.search, and it costs 3 credits. No return format, pagination, or rate-limit detail is given beyond the credit cost.

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?

Three short sentences, zero waste, with the core purpose front-loaded and the sibling comparison and cost placed after it.

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 5-parameter tool with 40% schema coverage and no output schema, the description handles the purpose, sibling relationship, return shape, and cost, but leaves three parameters and any pagination behavior unexplained. Adequate but with clear gaps.

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?

With only 40% schema description coverage, the description needs to compensate. It reinforces the required 'category' parameter's meaning but says nothing about 'page', 'country_code', or 'cache_max_age', which are undocumented in both the schema and the description.

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?

Uses a specific verb+resource ('Browse a Walmart category') and immediately scopes it as a 'Public Walmart category listing', then distinguishes it from walmart_search by keying on category id instead of a query. An agent can tell what it does and how it differs from the search sibling, though 'browse' alone would be vague without the second sentence.

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

Usage Guidelines4/5

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

The clause 'keyed by category id instead of a query' implicitly routes the agent: use walmart_search for keywords, this tool for category ids. Clear context, but there is no explicit 'when not to use' or statement of prerequisites (e.g., how to obtain a category id beyond the schema example).

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.