Skip to main content
Glama
Sign In
pregamer189

warframe-builds-mcp

by pregamer189
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

suggest_warframe_build

Read-onlyIdempotent

Suggests Warframe, companion, Archwing, or Necramech mod builds that meet stat goals and targets within capacity, polarity, and mod conflict limits.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
auraNoAura mod name or {name, rank, slot_polarity}.
goalNoOne stat, or weights such as {strength: 2, efficiency: 1}. Stats: strength, duration, range, efficiency, health, shields, armor, energy or effective_health.
modsNoMods that must be in the build.
formaNoExtra Forma you are willing to add. The result lists the polarities to add. Default 0.
levelNoThe item's rank, which sets its capacity. Default 30. Kuva and Tenet-style weapons and Necramechs can reach 40.
exilusNoExilus mod name or {name, rank, slot_polarity}.
arcanesNoArcane names or {name, rank} objects. Their triggered effects count when conditionals is true.
excludeNoMods not to use, such as ones you do not own.
reactorNoOrokin Reactor installed. Default true.
targetsNoMinimums to reach first, such as {efficiency: 175, strength: 145}. Results list any it could not reach.
warframeYes
base_statsNo
polaritiesNoThe frame's current slot polarities, if you have added Forma. Defaults to its own.
use_exilusNoPick an Exilus mod if none is named. Default true.
second_auraNoJade only. Second aura mod name or {name, rank, slot_polarity}.
conditionalsNoCount triggered effects, such as Galvanized mods and arcanes, at full stacks. Gives a peak figure. Default false.
archon_shardsNoShards to include, as a stat name or {stat, tauforged}.
extra_effectsNoExtra percentage bonuses for buffs this tool cannot see, by effect name, such as {damage: 50, critChance: 25}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations establish the safety profile (readOnlyHint: true, destructiveHint: false). The description adds crucial functional context by explaining that it manages complex interactions like capacity, polarities, and conflicts, which are behavioral traits not captured by simple safety hints.

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?

The definition is efficient. The first sentence front-loads the core functionality and its scope, while the second sentence concisely summarizes the data points it handles, achieving maximum information density without unnecessary padding.

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

Completeness3/5

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

Given the complexity and number of parameters (18), the description adequately explains *what* the tool does and *how* it calculates results. However, it lacks completeness regarding the structure or ambiguity of the output, such as whether it returns a single best build or a list of viable options.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With high schema coverage (89%), the baseline is strong. The description adds specific value by explicitly listing the exact stat types that can be referenced in the goal and targets (e.g., 'efficiency', 'effective_health'), reinforcing the allowed semantic vocabulary for complex input parameters.

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 specifies the exact action ('Suggest mods') and the resources it affects ('Warframe, companion, Archwing or Necramech'). It clearly defines the operational constraints by mentioning goals, targets, capacity, polarities, and conflicts, making it easy to distinguish from general 'build' tools.

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 implicitly tells the agent two usage paths: optimizing toward a 'goal' or achieving minimum 'targets'. However, it offers no guidance on when to use this highly complex tool versus simpler alternatives like 'warframe_build' or 'search_mods' from the sibling list.

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

Deploy Server

Other Tools