Skip to main content
Glama

AgentShopping

list_merchants

List stores in the merchant directory: categories they sell, markets, currencies, price band, coupons, affiliate network, and /go/ shop links. sample=true means the store is seeded example data, not a live feed.

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_merchants"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does usefully disclose the shape of the returned records and, importantly, that sample=true marks seeded example data rather than a live feed — valuable provenance context an agent could not get elsewhere. It says nothing about result size, pagination, ordering, or whether the whole directory is returned in one call, which matters for a listing tool with no parameters.

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 sentences, front-loaded with the verb and resource, then the returned fields. The field enumeration is dense but each item carries information. The only structural weakness is the dangling 'sample=true' clause, which reads as an input reference and slightly muddies an otherwise clean layout.

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?

With no annotations, no parameters, and no output schema, the description has to explain both what comes back and how it behaves; it does the former well by listing the record fields. It omits volume and pagination behavior, which is the main open question for a parameterless directory listing. The phantom sample parameter also leaves the agent unsure whether it is an input or a returned field.

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?

The schema declares zero properties, which would normally set a baseline of 4, but the description references 'sample=true' — a parameter that does not exist in the input schema. That is a genuine inconsistency an agent could act on by attempting to pass an argument the tool will reject. The explanation of what sample means is otherwise clear, but it should be framed as an output field, not an input.

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 uses a specific verb ('List') with a specific resource ('stores in the merchant directory') and enumerates the fields each entry carries (categories, markets, currencies, price band, coupons, affiliate network, /go/ links). That is well beyond a restatement of the name. It stops short of explicitly contrasting itself with the sibling 'find_stores_for', so an agent must infer the difference between a raw listing and a filtered lookup.

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 statement of when to call this versus 'find_stores_for', 'search_offers', or 'list_coupons'. The only usage-adjacent note is what sample=true signals, which is a data-provenance hint rather than when-to-use guidance. The implied use case (browsing the whole directory) is left for the agent to infer.

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