Skip to main content
Glama

Get a store's current offers

get_store_offers
Read-onlyIdempotent

List one store's current coupon codes and deals, soonest ending first, optionally for one country. Returns up to 10 offers with code (or none), end date, countries and links, plus the store's total number of offers and a link to all of them on Coupossum.

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": {
      "store": "<store>"
    },
    "name": "get_store_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeYesStore name, domain or Coupossum store slug
countryNoISO country code, e.g. CH or US. Returns offers for that country plus worldwide ones.

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?

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description adds real behavioral context beyond them: results are capped at 10, sorted soonest-ending first, and the response includes the store's total offer count plus a link to the full list. It stops short of covering not-found behavior or whether the 'none' code case means a deal without a coupon.

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?

One dense sentence that front-loads the operation, scope and ordering, then the return shape. Every clause carries information and nothing is padded.

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?

With no output schema, the description usefully enumerates the returned fields and the result cap, and the two parameters are fully specified in the schema. The only gaps are edge behavior — unknown store, or whether the 10-offer cap is pageable — which are minor for a read-only lookup.

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 country's worldwide-inclusion rule. The description only restates that country is optional, adding little beyond the schema; 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?

The description gives a specific verb and resource ('List one store's current coupon codes and deals'), plus ordering and default cap. The 'one store's' framing implicitly contrasts with the search_* siblings, but it never names an alternative, so an agent must infer the split between this and search_coupons.

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 rather than stated: you call this when you already have a single store in hand. There is no explicit when-not guidance, no mention of what to do if the store name is ambiguous, and no routing to search_coupons/search_stores for broader queries.

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.