Skip to main content
Glama
Sign In
pregamer189

warframe-builds-mcp

by pregamer189
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

weapon_build

Read-onlyIdempotent

Calculate Warframe weapon, Zaw, or Kitgun builds: damage types, crit, status, DPS, mod capacity, and enemy-target results. Include melee combo/heavy-attack stats.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
zawNoA Zaw from parts: {strike, grip, link}. See list_modular_parts.
modsNoMod names, or {name, rank, slot_polarity} objects. Rank defaults to max. Use slot_polarity "none" for an empty slot.
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, such as Incarnon Form. Defaults to the first.
exilusNoExilus mod name or {name, rank, slot_polarity}.
kitgunNoA Kitgun from parts: {chamber, grip, loader}. See list_modular_parts.
stanceNoMelee only. Stance mod name or {name, rank, slot_polarity}. Adds capacity and gives per-combo DPS. Defaults to the weapon's stance polarity.
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.
catalystNoOrokin Catalyst installed. Default true.
base_statsNoOverrides: damage (by type), critChance, critDamage, statusChance, fireRate, pellets, magazine, reload, ammoCost, heavyAttack, range, windUp.
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. Scales heavy attacks, Blood Rush and Weeping Wounds.
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 readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful behavioral detail by listing computed outputs and noting that melee results include range, heavy attacks, and per-combo stance DPS, but it does not disclose error behavior, data assumptions, or limitations beyond that.

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 description is three compact sentences and front-loads the core purpose and result categories. The final sentence about passing target is slightly redundant with the schema but still useful as a usage cue, so it is mostly efficient.

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 complex 17-parameter calculator with nested objects and no output schema, the description gives a strong summary of what results include and how melee differs. It does not cover alternative-tool routing, but the schema handles parameter details thoroughly and the description supplies enough output context for correct invocation.

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 the schema already documents all 17 parameters in detail, including nested shapes and defaults. The description’s only parameter-related addition is the target hint, which largely restates the schema’s own target description; baseline 3 is appropriate.

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 uses a specific verb (Calculate) and resource (weapon, Zaw or Kitgun build) and enumerates the computed outputs, so an agent can tell what the tool produces. It does not explicitly distinguish itself from the sibling suggest_weapon_build, which could be a source of selection ambiguity.

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?

Usage guidance is implied rather than explicit: the description says to pass target for enemy damage calculations, but it does not state when to choose this tool over suggest_weapon_build or other siblings. There are no when-not-to-use conditions or named alternatives.

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