warframe-builds-mcp

Overview Schema Source Related Servers Discussions Admin

explore_loadout

Read-onlyIdempotent

Build a complete Warframe loadout by combining a Warframe, subsumed ability, weapons, and companion with their facts, mods, and rules.

Instructions

The whole character for one job: Warframe, subsume, weapons and companion together. Returns each part's facts, abilities that touch weapons, fitting subsumes with what changes when subsumed, companion mods and the rules for every part. Use it when building a full loadout, or when a player doesn't want a subsume or companion.

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": {
      "warframe": "<warframe>"
    },
    "name": "explore_loadout"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Most subsumes and companion mods to list. Default 8.
`theme`	No	What it's for: nuke, tank, buff, armor, energy, control, support, stealth, or words from the game's text. Ranks the subsumes.
`subsume`	No	An ability infused through the Helminth: {ability, replaces}, such as {ability: "Roar", replaces: "Molt"}. See explore_loadout.
`weapons`	No	Weapon names, or {weapon}, {zaw} or {kitgun} objects.
`warframe`	Yes
`companion`	No	A companion, such as Smeeta Kavat.
`no_subsume`	No	The player doesn't want a subsume.
`no_companion`	No	The player doesn't want a companion.
`companion_weapon`	No	A sentinel weapon or beast claws.

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 declare readOnlyHint/idempotent/non-destructive, so safety is covered. The description adds genuinely useful non-annotation behavior: it discloses the return contents (part facts, weapon-touching abilities, subsumes with what changes when subsumed, companion mods, per-part rules), which matters because there is no output schema.

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 scope statement, then the return contract, then the usage trigger. The middle sentence is a long comma-separated enumeration but every item is informative; there is minimal filler.

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?

For a 9-parameter tool with a nested subsume object and no output schema, the description covers both what comes back and when to reach for it. It could be tighter on how theme ranks subsumes and on boundaries versus build-suggestion siblings, but nothing essential for correct invocation is missing.

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 89%, so the schema already explains limit, theme, subsume, companion_weapon, and the no_* flags in detail. The description adds little parameter-specific meaning beyond reinforcing that subsume/no_subsume/no_companion are legitimate ways to shape the result, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb-plus-resource: it assembles one complete character/loadout (Warframe, subsume, weapons, companion) for a job. It distinguishes itself from narrower siblings like suggest_warframe_build or weapon_build by the phrase 'The whole character for one job', though it never names those siblings explicitly.

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

Usage Guidelines4/5

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

'Use it when building a full loadout, or when a player doesn't want a subsume or companion' gives a clear triggering context and covers the no_subsume/no_companion case. It stops short of naming alternatives (e.g. suggest_warframe_build for a frame-only request), so the agent must infer the boundary.

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