Warframe MCP Server

by RainRaini4

Overview Schema Source Related Servers Discussions Admin

TypeScript

lookup_mod

Look up Warframe mods by name to view stats progression, polarity, drain, rarity, and drop locations.

Instructions

Look up one or more mods by name: stats progression, polarity, drain, rarity, and drop locations.

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_mod"
  }
}

Input Schema

Name	Required	Description	Default
`names`	Yes	Mod name(s) (e.g. ['Serration', 'Primed Continuity'])

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A3.9/5.0

Behavior3/5

Does 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 what the tool returns but does not mention behavioral traits like idempotency, error handling, or rate limits. Adequate for a simple lookup tool, but missing some context.

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 sentence that efficiently conveys the tool's purpose and output. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup tool with one parameter and no output schema, the description is complete, specifying the exact information returned (stats, polarity, drain, rarity, drop locations).

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 description coverage is 100%, providing example values. The description adds the list of returned fields but no additional parameter semantics beyond what the schema already provides. 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 'Look up one or more mods by name' with specific verb and resource, and lists the return fields (stats progression, polarity, drain, rarity, drop locations). It distinguishes from sibling lookup tools like lookup_warframe and lookup_weapon.

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 usage for known mod names but provides no explicit guidance on when to use versus alternatives like search_drops or relic_drops. No when-not-to-use or alternative tool naming.

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