Skip to main content
Glama

ShopAt UK Deals

List stores

list_stores
Read-only

List UK retailers that currently have deals on ShopAt, with slugs, domains and deal counts. Optional name search.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the meaningful constraint that only retailers with current deals are returned, plus the shape of each result. It says nothing about the limit parameter's effect, truncation, or ordering, which matter for a list endpoint.

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?

Two short sentences with the scope and return fields front-loaded and no wasted wording. The trailing 'Optional name search' earns its place as a usage hint but is the only part that feels tacked on.

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

Completeness3/5

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

For a simple read-only listing tool with annotations covering safety and no output schema, stating the returned fields largely suffices. The gaps are the undocumented limit/pagination behavior and the unspecified search matching semantics, which an agent needs to call it confidently.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only glosses 'q' as an optional name search (no indication of prefix vs substring vs exact matching) and never mentions 'limit', despite its default of 50 and cap of 200.

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 ('List UK retailers') plus a scope qualifier ('that currently have deals on ShopAt') and the fields returned (slugs, domains, deal counts). An agent can tell this is a store directory rather than a deal search, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives such as search_deals or list_categories. 'Optional name search' hints at a filtering mode but does not say when to prefer browsing the store list over searching deals.

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