warframe-builds-mcp

Overview Schema Source Related Servers Discussions Admin

special_rules

Read-onlyIdempotent

Find hidden Warframe mechanics and item interactions that game text and wiki do not explain, including sources, dates, patch status, and build-item rules.

Instructions

Find mechanics that players reported in videos and the game's text doesn't explain, such as hidden multipliers, unexpected stacking and interactions, each with its date, source and what later patches and the wiki say. Search by item, ability or idea, such as "condition overload", "gas" or "slam". Build results also list the rules for the items they use.

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": "special_rules"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Most rules to return, up to 60. Default 20.
`query`	No	Words that must all appear in the rule. Leave out to browse.
`status`	No	Only rules with this status.
`surprising_only`	No	Only rules that go beyond what the game or wiki explains plainly. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.12.0Nov 3, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description usefully spends its words on result content instead: each rule carries a date, source, later-patch status, and wiki commentary, and build queries also return the rules for items in the build. It stops short of describing pagination or ordering behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Three sentences, front-loaded with the core purpose and followed by search guidance and a result-content note. Every sentence carries information, though the 'build results also list...' sentence is a slight add-on rather than core.

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?

With no output schema, the description is responsible for return values and does so (date, source, patch outcomes, wiki notes, incidental build rules). The main remaining gap for a no-required-parameter, browse-able tool is the meaning of the status filter values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all four parameters are already documented, including the status enum and the 60-item limit. The description adds meaning only for query, clarifying that it accepts item, ability, or concept terms with examples, and never explains what the status values (e.g. 'contradicted' vs 'fixed') signify.

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?

The description states a specific verb and resource: find mechanics that players reported but the game's text doesn't explain, with concrete examples (hidden multipliers, unexpected stacking). It distinguishes the tool from the sibling record_mechanic/forget_mechanic pair by framing it as a discovery/search operation over undocumented rules.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is conveyed mainly through example queries ('condition overload', 'gas', 'slam'), which tells the agent what kinds of input work. There is no explicit statement of when to prefer this over record_mechanic, explore_synergies, or build_guide, and no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.