Find Warframe mods by name, effect, or effect text, with optional category and PvP filters, to identify mods for a build.
Search mods by name, effect (for example strength or multishot) or effect text. Leaves out PvP-only mods unless asked.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | ||
| category | No | ||
| include_pvp | No | Include Conclave-only mods. Default false. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this as a safe, read-only, idempotent search. The description adds a meaningful behavioral detail beyond annotations: PvP-only mods are excluded by default unless requested, which affects result interpretation.
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, front-loaded and free of filler. The default PvP exclusion is placed after the core search behavior where it is easy to scan.
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 read-only search tool with annotations and no output schema, the description covers the essential purpose and the key default filtering behavior. It is slightly thin on category semantics and result limiting, but those gaps are minor.
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 coverage is only 25%, and the description partially compensates by explaining that the query can match mod name, effect name, or effect text. It does not clarify the category or limit parameters, so important semantics remain undocumented.
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?
States a specific verb and resource ('Search mods') plus the searchable fields (name, effect, effect text). It is clear what the tool does, though it does not explicitly differentiate itself from sibling search/list tools such as search_arcanes.
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?
Usage is implied by the search-by-fields phrasing, and the description notes the default PvP exclusion. However, it gives no explicit guidance about when to choose this tool over alternatives or what happens when the query is broad.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.