warframe-builds-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_warframesA | Find Warframes, companions, Archwings or Necramechs by name, with stats, polarities and abilities. |
| list_weaponsB | Find primary, secondary, melee, Exalted, Archwing and companion weapons by name or type, with attack modes and stats. |
| list_modular_partsA | List the parts for building a Zaw or Kitgun with weapon_build. |
| search_modsA | Search mods by name, effect (for example strength or multishot) or effect text. Leaves out PvP-only mods unless asked. |
| search_arcanesB | Search arcanes by name or effect text. |
| warframe_buildA | Calculate a Warframe, companion, Archwing or Necramech build: final stats, ability stats, armor mitigation and mod capacity. |
| weapon_buildA | Calculate a weapon, Zaw or Kitgun build: damage by type, crit, status, damage over time, DPS and mod capacity. Melee results add range, heavy attacks and per-combo stance DPS. Pass target for damage against an enemy. |
| suggest_weapon_buildA | Suggest the mods that give a weapon, Zaw or Kitgun the most damage, within its capacity, polarities and mod conflicts. Pass target to pick for a specific enemy instead of raw damage. |
| suggest_warframe_buildA | Suggest mods for a Warframe, companion, Archwing or Necramech towards a goal or targets, within capacity, polarities and conflicts. Stats: strength, duration, range, efficiency, health, shields, armor, energy or effective_health. |
| data_infoA | Show the server version, when the game data was imported, what it covers and its limits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Tools separate cleanly into lookup (list_*/search_*), calculation (_build), and recommendation (suggest_*_build) roles. The closest pair, warframe_build vs suggest_warframe_build, is distinguished by their descriptions (evaluating supplied mods vs. proposing mods), and weapon_build/suggest_weapon_build mirror that split. Only list_modular_parts sits slightly apart as a sub-lookup for weapon_build, but its description ties it back.
The set mixes verb_noun forms (list_warframes, search_mods) with noun-first forms (warframe_build, weapon_build) and a suggest_ prefix. The pairing is at least internally symmetric (warframe_build/suggest_warframe_build, weapon_build/suggest_weapon_build), so it stays readable. However, a uniform pattern like calculate_warframe_build or list_modular_parts vs weapon_parts would be cleaner.
Ten tools is well within the sweet spot. Each one maps to a distinct step in the build-planning workflow: enumerate entities, search mods/arcanes, compute stats, and get suggestions. Nothing feels padded or redundant.
The surface covers the full loop of finding frames/weapons/mods/arcanes, calculating stats, and recommending builds, including modular weapons and target-aware damage. Minor gaps remain: no enemy/target lookup tool despite 'target' parameters, and no way to enumerate mods by slot, polarity, or compatibility beyond free-text search, which may force guesswork.