Skip to main content
Glama

CouponBricks verified coupons

Find a store

search_stores
Read-only

Find online stores on CouponBricks by name (e.g. "helium 10", "saunaspace"). Returns the store name, its slug for get_coupons, how many live offers it has, and its coupon 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": {
      "query": "<query>"
    },
    "name": "search_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesStore name or part of it.
countryNoShopper's country as a 2-letter code: US, IN, AE, SG, MY or JP. Any other value (or none) uses the CouponBricks global site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds useful behavioral context: it is a name-based search, it returns live offer counts, and it yields the slug needed for coupon retrieval. It omits pagination or result-limit behavior, but for a read-only lookup tool this is a minor gap.

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 dense sentence front-loads the action and lookup key, then enumerates the return fields. Examples are embedded efficiently and every clause carries useful information.

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?

For a simple two-parameter read-only search, the description covers purpose, lookup key, return values, and the critical handoff to get_coupons. Since no output schema exists, listing the returned fields is particularly valuable; only minor details like result limits are absent.

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 description coverage is 100%, so both query and country are already fully documented in the schema. The description reinforces the name-search behavior with examples and explains the role of the returned slug, but adds no country semantics beyond what the schema states.

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?

States a specific verb and resource (find online stores on CouponBricks) plus the lookup key (store name) with concrete examples. It also distinguishes itself from get_coupons by noting that the returned slug is used for get_coupons.

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 description makes clear this is the lookup step when you know a store name, and explicitly connects its slug output to get_coupons. It does not state any exclusions or when-not-to-use conditions, but the context is sufficiently clear.

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