list_marketsLists every third-party marketplace covered by the steamwebapi.com market price endpoints, with their domain and the games they cover.
| Name | Required | Description | Default |
|---|---|---|---|
| game | No | Restrict to markets that cover a specific game slug, e.g. "cs2". |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that the tool returns an exhaustive list ('every') and includes the specific output fields (domain and games covered). This implies a read-only operation without side effects, which is adequate for a list tool, though it does not mention potential auth or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that leads with the action and resource, then specifies the output. Every piece of information is relevant and there is no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (one optional parameter, no output schema) and the description covers the core behavior: what is listed and what fields are returned. It could mention whether pagination is involved, but for a list of markets this is likely unnecessary. Overall, it is sufficiently complete for an agent to understand the tool's function.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, so the single optional parameter 'game' is fully documented in the input schema. The description adds no additional parameter semantics, which is acceptable given the high schema coverage baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a clear verb 'Lists' and a specific resource 'third-party marketplace covered by the steamwebapi.com market price endpoints'. It also specifies what is returned (domain and games they cover), fully distinguishing it from sibling list tools like list_endpoints or list_games.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies when to use the tool: to obtain all third-party marketplaces supported by the market price endpoints. Although it doesn't explicitly say 'use this instead of X', the resource and scope are unambiguous enough to guide selection among similar list tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource/action: execution, concept lookup, endpoint spec, pricing, and enumeration of games, markets, products, endpoints, and concepts. No overlapping purposes.
All tools follow a consistent verb_noun snake_case pattern (call_, get_, list_, search_), making the naming predictable and easy to navigate.
10 tools is well-scoped for an API exploration server, covering execution, lookup, search, enumeration, and pricing without redundancy.
The server covers the full workflow: discover endpoints, search concepts, list supported games/markets/products, retrieve detailed specs and pricing, and execute readonly API calls. No obvious gaps for its intended purpose.