Skip to main content
Glama

Shop List

shop_list

List the e-shops and APIs the owner connected on ecomdly (name, platform, whether you may change data, the skill that explains its API — or via: mcp for a Shoptet shop connected through Shoptet MCP, used with shop_tools and shop_call; for a custom API also its base address and the owner's description of it). Pass the name as shop to shop_request, shop_tools or shop_call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/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, and it does disclose meaningful traits: that the result includes a permission indicator ("whether you may change data") and that entries may be either a documented API with a skill or a proxied Shoptet MCP shop. Read-only listing with no pagination or failure-mode notes keeps it short of a 5.

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?

One front-loaded sentence with the core action first and the field enumeration in a parenthetical. The nesting of the `via: mcp` clause makes it dense on first read, but every clause carries information an agent needs.

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 correctly compensates by naming the returned fields, including conditional ones (base address and owner description for custom APIs). Nothing critical is missing for a zero-argument discovery tool, though a note on what an empty list means would close the last gap.

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, which is the baseline-4 case. The `shop` naming note refers to how returned values feed sibling tools rather than to any input, so no parameter semantics are needed or missing.

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?

Opens with a specific verb and resource ("List the e-shops and APIs the owner connected") and then enumerates the returned fields, so the agent knows exactly what it gets. The mention of `via: mcp` for Shoptet shops further scopes what 'shop' means here versus a plain API.

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?

Explicitly routes the agent forward: "Pass the name as `shop` to shop_request, shop_tools or shop_call", which tells it this is the discovery step before invoking a shop. It doesn't explain when to prefer it over the sibling api_list, so the division of labour between the two list tools stays implicit.

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