Skip to main content
Glama

Search stores by name

get_stores_by_name
Read-onlyIdempotent

Searches stores by name and returns the matching stores' identity only — store_id, name, country_code, website domain and GotCashback store page url — without cashback rates or gift cards. Use it when the user wants to know whether GotCashback covers a store, in which countries a store is listed, or when you need a store_id for the account tools (toggle_favorite_store, set_store_alert). For any question about cashback rates or gift card discounts call get_cashback_rates_by_store_name or get_gift_cards_by_store_name directly instead — they search by name themselves, so this tool is not a required first step. Returns matches best first; empty when nothing matched. When presenting stores, include each store's 'url' as a clickable link (and 'gift_cards_url' when present).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_nameYesThe retailer or brand name as a shopper would say it, e.g. 'Walmart', 'Nike', 'Best Buy', 'Expedia', 'Home Depot'. Matched case-insensitively at word boundaries of the store name and its known alternate names (exact name, then names starting with it, then names containing it as a word), best match first; a partial-word match (e.g. 'gap' inside 'Singapore') is only returned when nothing better exists. Pass the plain name only — no words like 'cashback', 'gift card' or a country.
country_codeNoOptional. Lowercase ISO 3166-1 alpha-2 country code that limits results to one country, e.g. 'us' (United States), 'ca' (Canada), 'gb' (United Kingdom — use 'gb', not 'uk'), 'de' (Germany), 'au' (Australia), 'fr' (France). Pass it when the user names a country ('in Canada', 'UK cashback'); omit it to search all supported countries.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
storesNoMatching stores (one entry per country). Empty when nothing matched.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / store_name / description
      Previous value: -"The retailer or brand name as a shopper would say it, e.g. 'Walmart', 'Nike', 'Best Buy', 'Expedia', 'Home Depot'. Matched as a case-insensitive substring of the store name and its known alternate names, best match first. Pass the plain name only — no words like 'cashback', 'gift card' or a country."New value: +"The retailer or brand name as a shopper would say it, e.g. 'Walmart', 'Nike', 'Best Buy', 'Expedia', 'Home Depot'. Matched case-insensitively at word boundaries of the store name and its known alternate names (exact name, then names starting with it, then names containing it as a word), best match first; a partial-word match (e.g. 'gap' inside 'Singapore') is only returned when nothing better exists. Pass the plain name only — no words like 'cashback', 'gift card' or a country."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds meaningful behavior beyond those: match ordering (best first), case-insensitive word-boundary matching, empty-result behavior, and a presentation requirement (include 'url' as clickable link). These are not inferable from annotations alone.

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?

The description is information-dense with no filler. Each sentence earns its place: return scope, use cases, sibling routing, ordering, empty behavior, and link presentation. Critical routing information is front-loaded, and parameter details are left to the schema. Excellent structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, idempotent search tool with a fully documented schema and an output schema present, the description covers everything needed for correct selection and invocation. It addresses scope, alternatives, result ordering, empty results, and presentation. Nothing an agent needs is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema fully documents store_name and country_code. The description reinforces the key semantic point that store_name should be a plain retailer name without qualifiers like 'cashback' or 'gift card', and it ties country_code usage to user mentions of a country. This adds slight value beyond the schema but not enough for a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with a specific verb and resource ('Searches stores by name') and immediately narrows the scope to 'identity only' fields, explicitly excluding cashback rates and gift cards. It also names the sibling tools (get_cashback_rates_by_store_name, get_gift_cards_by_store_name) that handle those excluded areas, making differentiation explicit.

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

Usage Guidelines5/5

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

The description states clear when-to-use conditions: checking store coverage, countries, or obtaining a store_id for account tools. It also provides explicit when-not-to-use guidance by directing cashback and gift card questions to dedicated sibling tools and clarifying that this tool is not a required first step. This is strong routing guidance.

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