Skip to main content
Glama
Sign In
shelfatlas-mcp

shelfatlas-mcp

by SlambertDK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_chains

Retrieve all retail chains available in the ShelfAtlas catalog so you can identify which grocery chains are covered before querying offers or stores.

Instructions

List all retail chains available in the ShelfAtlas catalog.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it only hints that the result is exhaustive via "all". It says nothing about whether the list is paginated, ordered, cached, or whether authentication is required to read the catalog.

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 11-word sentence with the resource front-loaded and zero filler. Nothing to trim and nothing buried.

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 trivial zero-param read the description is minimally sufficient to invoke, but with no output schema and no annotations it leaves the return shape (chain names? IDs? objects with metadata?) and any sibling relationship unexplained.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter semantics to document and the description correctly signals the call is unfiltered.

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?

Specific verb + resource: "List all retail chains available in the ShelfAtlas catalog" clearly identifies an enumeration of chain entities. It does not, however, distinguish itself from the sibling get_stores, which an agent could plausibly confuse with a chain-listing operation.

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?

No when-to-use guidance, no exclusions, and no mention of the sibling tools (get_stores, search_catalog_offers) that overlap with this one. The zero-parameter signature implies a lookup/reference call, but that is inference rather than stated guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools