Locate installed Steam games by scanning configured library folders. Optionally filter results by name to find a specific title.
Search configured Steam library paths for installed games. Optionally filter by name.
| Name | Required | Description | Default |
|---|---|---|---|
| filter | No | Optional name filter (case-insensitive partial match) |
Changes observed during successful MCP inspections.
v0.1.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It reveals that search targets configured Steam library paths, but does not state whether the operation is read-only, whether it can be slow or require Steam to be configured, or what side effects (if any) exist.
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?
Two short sentences with zero waste, front-loading the core purpose before the optional parameter. Every sentence earns its place.
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 low-complexity, single-parameter tool with no output schema and no annotations, the description covers the essential purpose and parameter. It could still hint at return shape or read-only nature, but the core information needed to invoke it is present.
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?
Schema description coverage is 100%, and the sole parameter already documents itself as an optional case-insensitive partial match. The description only restates 'Optionally filter by name,' adding no extra parameter meaning.
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 states a specific verb ('Search'), resource ('installed games'), and scope ('configured Steam library paths'). It is clearly distinguishable from all sibling tools, none of which deal with listing or finding Steam 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 says what the tool does but gives no guidance on when to use it versus alternatives. It only mentions an optional parameter, not when a search is appropriate or what prerequisites exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.