Skip to main content
Glama

Dorm Kit – hand-picked gift ideas

List marketplaces

list_marketplaces

List supported Amazon storefronts (id, domain, defaultLocale). Match marketplace + locale to the end user: amazon.com (tag sw-dormkit-20) for the US, amazon.se (tag sw-dormkit-21) for Sweden.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does disclose the return shape and an operational detail an agent could not otherwise infer (per-marketplace affiliate tags). It does not state that it is read-only, whether the list is static, or how results are ordered, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler. The scope and return fields come first, the selection guidance and examples second, so the agent gets the essentials immediately.

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?

No output schema exists, and the description compensates by enumerating the returned fields, which is what an agent needs to chain this into a marketplace-scoped call. It leaves open how many marketplaces exist and whether the US/Sweden examples are exhaustive.

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 and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the field list it mentions is return data, not input semantics.

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?

Specific verb (List) plus a precisely scoped resource (supported Amazon storefronts) and it even names the returned fields (id, domain, defaultLocale). That distinguishes it cleanly from siblings such as health, list_catalog_items, and resolve_product.

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?

"Match marketplace + locale to the end user" tells the agent the selection criterion to apply once results arrive, with concrete US/Sweden examples. It stops short of naming which sibling call should consume this result (e.g., resolve_product or list_catalog_items), so it's clear context rather than a full routing rule.

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