Skip to main content
Glama

Shops and shop onboarding

shops

action: list (compared shops with ratings), then for a shop joining: check_feed, register, status, verify_domain, diagnostics; mine and statistics need the owner's sign-in.

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": {
      "action": "<action>"
    },
    "name": "shops"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day YYYY-MM-DD (statistics)
fromNoFirst day YYYY-MM-DD (statistics)
shopNoShop slug or registration id
emailNoContact e-mail (register)
limitNoMax rows
tokenNoToken from a link or e-mail
actionYesOperation to run; help {topic:"shops"} lists each one's arguments
detailNocompact (default) or full
domainNoShop domain
offsetNoRows to skip
countryNoCountry code, e.g. CZ
feed_urlNoPublic feed address
affiliateNoown, ehub, cj, awin, other or none (register)
shop_nameNoShop name (register)
accept_termsNoAccept the partner terms (register)
terms_versionNoPartner terms version (register)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Operation to run; help {topic:\"shops\"} lists each one's arguments"
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "compact (default) or full",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Max rows",
      +  "type": "number"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip",
      +  "type": "number"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive behavior; the description adds an action-specific authentication requirement for mine and statistics and indicates that onboarding follows a sequence. It still does not disclose mutation side effects or what register and verify_domain actually change, so it is not 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?

It is one dense sentence, front-loaded with the action list, and every clause carries routing or prerequisite information. The semicolon-packed telegraphic style is slightly hard to parse but not wasteful.

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?

The tool has 16 parameters and 8 actions with no output schema; the description supplies an action map and an authentication note but no per-action argument mapping, return expectations, or pagination details. The 100% schema coverage compensates substantially, leaving it adequate but incomplete.

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 description coverage is 100%, so the baseline is 3; the description only repeats action names already present in the enum and adds no new meaning for shop, domain, feed_url, affiliate, terms, pagination, or date parameters.

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 names the resource (shops) and maps the action enum to listing, onboarding, and owner-only operations, so an agent can identify it as a shop listing/onboarding tool. It does not explicitly contrast with sibling tools, so it is not a 5.

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?

It gives a usage sequence for a shop joining: check_feed, register, status, verify_domain, diagnostics, and it states that mine and statistics require owner sign-in. It does not explicitly say when to choose this over sibling tools such as search, but the operational context is clear.

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