Skip to main content
Glama
Sign In
pregamer189

warframe-builds-mcp

by pregamer189
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

suggest_weapon_build

Read-onlyIdempotent

Generate a Warframe weapon, Zaw, or Kitgun mod build that fits capacity, polarities, and mod conflicts while maximizing damage; optionally tune it to a target enemy.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
zawNoA Zaw from parts: {strike, grip, link}. See list_modular_parts.
goalNoDefaults to sustained_dps for guns and burst_dps for melee. heavy_attack is melee only.
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.
rivenNoA Riven with your rolled stats: {effects, polarity, drain, slot_polarity}, such as {effects: {critChance: 120, multishot: 90}, polarity: "madurai", drain: 18}. Fills a regular slot.
attackNoAttack mode from list_weapons. Defaults to the first.
kitgunNoA Kitgun from parts: {chamber, grip, loader}. See list_modular_parts.
stanceNoMelee only. Defaults to a fitting stance, chosen only for its capacity.
targetNoThe enemy: {faction, armor}. Applies faction damage multipliers, armor reduction and faction mods. See data_info for factions.
weaponNoWeapon name. Use this, zaw or kitgun.
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.
catalystNoOrokin Catalyst installed. Default true.
polaritiesNoThe weapon's current slot polarities, if you have added Forma. Defaults to the weapon's own.
use_exilusNoThe weapon has an Exilus adapter. Default false.
conditionalsNoCount triggered effects, such as Galvanized mods and arcanes, at full stacks. Gives a peak figure. Default false.
extra_effectsNoExtra percentage bonuses for buffs this tool cannot see, by effect name, such as {damage: 50, critChance: 25}.
combo_multiplierNoMelee only. Combo multiplier from 1 to 12. Default 12.
status_types_on_targetNoStatus types on the enemy, for mods such as Condition Overload. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered and the description doesn't need to repeat it. It adds the useful behavioral fact that the result recommends polarities to add and that mods are chosen subject to capacity and conflicts. It does not describe what the returned suggestion actually contains (mod list, damage figure, forma count) — a notable gap since 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler. The core purpose is front-loaded, and the one optional usage tip follows immediately after. Nothing is wasted and nothing is buried.

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?

For a 20-parameter tool with nested objects (zaw, kitgun, riven, target) and no output schema, the description is thin: it never outlines the shape of the returned build suggestion or how the competing optimization goals are resolved. The schema covers inputs thoroughly, but the output side rests entirely on the description, which gives it only a passing mention.

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%, so all 20 parameters are already documented in the schema, including defaults and enum values. The description adds only marginal semantics ('target' switches from raw damage to a specific enemy; capacity/polarity constraints bind the `forma`, `polarities` and `level` params). Baseline 3 is appropriate when the schema carries the detail.

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?

States a specific verb and resource: suggests mods maximizing damage for a weapon, Zaw, or Kitgun. The 'suggest' framing and the constraint vocabulary ('within its capacity, polarities and mod conflicts') distinguish it from the sibling weapon_build, which evaluates an existing build. It never names that sibling explicitly, so differentiation is inferred rather than stated.

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 second sentence gives a genuine routing hint — pass `target` for a specific enemy instead of raw damage — which is a use-case condition. However, there is no guidance on when to use this versus weapon_build, no prerequisites (weapon/zaw/kitgun are mutually exclusive per the schema but the description doesn't say so), and no exclusions.

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