Warframe MCP Server

Overview Schema Source Related Servers Discussions Admin

lookup_warframe

Look up Warframe details including stats, abilities, component drop sources, build requirements, and vault status by providing one or more Warframe names.

Instructions

Look up one or more Warframes by name: stats, abilities, component drop sources, build requirements, and vault status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "names": "<names>"
    },
    "name": "lookup_warframe"
  }
}

Input Schema

Name	Required	Description	Default
`names`	Yes	Warframe name(s) (e.g. ['Rhino Prime', 'Wisp'])

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It mentions the data returned, which is helpful, but does not disclose edge cases (e.g., unknown Warframe name), rate limits, or authentication needs. For a read-only lookup, this is adequate but not thorough.

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

Conciseness5/5

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

The description is a single, well-front-loaded sentence with no fluff. Every word adds value, clearly communicating the tool's purpose and output.

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?

Given the low complexity (1 required parameter, no output schema), the description provides sufficient information for an agent to select and invoke the tool. It lacks an example of the return format, but output schema is absent, so the description compensates reasonably well.

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?

The input schema covers 100% of parameters with a clear description of the 'names' array and an example. The tool description does not add extra meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states the verb "Look up" and the resource "Warframes," listing specific return details (stats, abilities, drop sources, build requirements, vault status). It distinguishes from sibling tools like lookup_weapon by focusing on Warframes.

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?

The description implies when to use the tool (to look up Warframes) but provides no explicit guidance on when not to use it or alternatives among the numerous sibling tools. The context signals show 18 siblings, so some usage direction would be helpful.

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