warframe-builds-mcp

Overview Schema Source Related Servers Discussions Admin

explore_synergies

Read-onlyIdempotent

Find themed or unusual Warframe builds by retrieving ability text, augments, and matching mods and arcanes, so you can reason through combinations standard calculators cannot model.

Instructions

Start here for a themed or unusual build, such as a Saryn spore nuker or a tanky Mesa. Returns ability text, augments, and the mods and arcanes whose wording fits, so you can reason about combinations the calculators cannot model. Works for anything in the game data, including new items.

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

Input Schema

Name	Required	Description
`zaw`	No	A Zaw from parts: {strike, grip, link}. See list_modular_parts.
`limit`	No	Most mods and most arcanes to return, up to 60. Default 12.
`theme`	No	What the build is for, in plain words: tank, nuke, status, crit, energy, support, speed, stealth, control, melee, ammo, aoe, or any word from the game's text.
`attack`	No	Attack mode from list_weapons. Defaults to the first.
`kitgun`	No	A Kitgun from parts: {chamber, grip, loader}. See list_modular_parts.
`weapon`	No	Weapon name. Use this, zaw or kitgun.
`warframe`	No	A Warframe, companion, Archwing or Necramech. Use this, weapon, zaw or kitgun.
`use_profile`	No	Respect the saved profile's missing and owned mods. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.12.0Nov 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description is not needed for safety. It adds real behavioral value instead: what comes back (ability text, augments, matching mods and arcanes), that it is wording-based rather than calculator-based, and that it covers new items. Limit behavior and result size are left to the 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 tight sentences, front-loaded with the 'start here' cue and ending with the scope guarantee. Nothing is redundant, though the middle clause about calculators is longer than strictly necessary.

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 an 8-parameter tool with nested Zaw/Kitgun objects and no output schema, the description conveys the return shape and the reasoning-oriented purpose well enough to call it correctly. The remaining gaps (how limit interacts with results, relative ordering of mods vs arcanes) are minor and partly covered by the schema.

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% with per-parameter descriptions including defaults and the mutually exclusive warframe/weapon/zaw/kitgun guidance. The description only echoes the theme concept at a high level and adds no format or selection detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (explore) and a specific resource (themed/unusual builds), and names the output (ability text, augments, mods, arcanes). The phrase 'combinations the calculators cannot model' sharply distinguishes it from the suggest_*_build, warframe_build and weapon_build siblings.

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?

'Start here for a themed or unusual build' plus the contrast with calculators gives a clear selection rule, and 'works for anything in the game data, including new items' broadens applicability explicitly. It stops short of naming the sibling tools or stating a when-not-to-use case, so it isn't a 5.

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