Skip to main content
Glama

AgentShopping

find_stores_for

Find which stores sell a category, optionally in one country. Returns price bands, coupons, networks and tracked_url shop links via /go/. Sample rows must not be cited as live prices.

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

Input Schema

NameRequiredDescriptionDefault
countryNoISO 3166-1 alpha-2
categoryYestoys, kids-gear or football

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the return contents (price bands, coupons, networks, tracked_url shop links via /go/) and adds a data-freshness caveat that sample rows must not be cited as live prices. It omits auth requirements, rate limits, and result-size behavior, which keeps it from a 5.

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, front-loaded with the core purpose, then return shape, then the citation caveat. No filler and every sentence contributes information the agent needs.

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?

No output schema exists, so the description correctly explains what comes back, and for a two-parameter lookup that is nearly sufficient. Minor gaps remain around result volume and pagination, but nothing essential to invoking it correctly is missing.

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 both parameters are already documented, including the ISO 3166-1 alpha-2 format and the category values. The description only reinforces that country is optional, adding little beyond the schema, so the baseline 3 applies.

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 which stores sell a category") plus scope ("optionally in one country"), which is enough to separate it from siblings like list_merchants or search_offers. It stops short of explicitly naming an alternative, but the resource-level specificity is clear.

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?

Usage is implied by the phrasing: use it when you need to know which stores carry a given category, with country as an optional narrowing. There is no explicit when-not guidance or named alternative among the sibling tools, so the agent must infer selection.

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