Skip to main content
Glama

Find a store

find_store
Read-only

Find stores on CouponSwift by brand name, store slug or website domain (for example "hostinger", "bunny.net" or "https://www.nordvpn.com/pricing"). Returns up to 5 matching stores, best match first. For each store: its name, its category, the highest percentage discount among its current offers (null when no offer states a percentage), the number of active offers on its page, and the link to that page. The coupon codes themselves are not returned: open the store page to see them.

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

Input Schema

NameRequiredDescriptionDefault
queryYesA brand name, a store slug or a website domain or URL, 2 to 80 characters.

Output Schema

NameRequiredDescriptionDefault
storesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 genuine behavior beyond that: a hard result cap of 5, best-match-first ordering, and the null convention when no offer carries a percentage. The explicit statement that coupon codes are excluded prevents a common wrong assumption about what comes back.

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?

Front-loaded with the verb, resource, and identifier forms, then the result semantics, then the exclusion. Every sentence is informative, though the enumerated return fields partly duplicate the output schema and could be trimmed.

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 single-parameter lookup with annotations and an output schema already in place, the description covers purpose, input forms, result cardinality, ordering, and the key content exclusion. Nothing an agent needs in order to call it correctly 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% and the schema already constrains the query to 2-80 characters, so the baseline is 3. The description earns a bump by demonstrating the accepted shapes with real examples ('hostinger', 'bunny.net', 'https://www.nordvpn.com/pricing'), showing that full URLs with paths are valid input, which the schema does not make obvious.

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 (find) and resource (stores) and scopes the accepted identifiers to brand name, store slug, or website domain, backed by three concrete examples including a full URL. An agent immediately knows the resolution task this tool performs.

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?

Clear context for when to reach for it: you hold an identifier (brand, slug, domain/URL) and want the matching store records. It also closes the loop by pointing out that coupon codes are not returned and that the store page must be opened instead, which implicitly routes the agent to a follow-up action. No explicit exclusions or named alternatives, so not a 5.

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.