Search video games by name to find their SteamGridDB IDs, used for retrieving visual assets.
Search for video games on SteamGridDB by name. Returns a list of matching games with their SteamGridDB IDs, which can be used to retrieve visual assets.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The game name to search for |
Changes observed during successful MCP inspections.
v0.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the output type (a list of games with IDs) but lacks any information on rate limits, authentication, pagination, or side effects. As a search tool it is presumably read-only, but that is not stated. The description provides minimal behavioral context beyond the obvious.
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, efficient sentence that front-loads the action and resource, then adds the key outcome. No redundant or filler content, every word contributes to understanding.
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?
For a simple one-parameter search tool with no output schema, the description adequately explains what it does and what the result looks like. It does not mention optional filters or edge cases, but none are implied by the schema. Given the simplicity, the description is nearly complete.
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 for 'query' is already clear ('The game name to search for') and covers 100% of the single parameter. The description adds no further parameter-level details, only reiterating that the search is by name. Baseline of 3 is appropriate given high schema coverage.
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 clearly states a specific action ('Search') on a specific resource ('video games on SteamGridDB') and explains the result (list with IDs for retrieving assets). This distinguishes it from sibling tools like steam_search_game, which searches the Steam store, by explicitly naming SteamGridDB as the data source.
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 implies usage for retrieving visual assets by noting the IDs can be used for that purpose, but it does not explicitly state when to use this tool versus alternatives like steam_search_game or provide any exclusions. Usage guidance is implied rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.