Skip to main content
Glama
Sign In
pregamer189

warframe-builds-mcp

by pregamer189
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

warframe_build

Read-onlyIdempotent

Calculate Warframe, companion, Archwing, or Necramech builds to obtain final stats, ability stats, armor mitigation, and mod capacity.

Instructions

Calculate a Warframe, companion, Archwing or Necramech build: final stats, ability stats, armor mitigation and mod capacity.

Input Schema

NameRequiredDescriptionDefault
auraNoWarframes only. Aura mod name or {name, rank, slot_polarity}.
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.
exilusNoExilus mod name or {name, rank, slot_polarity}.
arcanesNoArcane names or {name, rank} objects. Their triggered effects count when conditionals is true.
reactorNoOrokin Reactor installed. Default true.
warframeYesName of a Warframe, companion, Archwing or Necramech.
base_statsNoOverrides for health, shields, armor or energy.
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_shardsNoUp to 5 shards, as a stat name or {stat, tauforged}: strength, duration, health, shields, armor or energy.
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

A3.6/5.0
Behavior4/5

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

The read-only, idempotent, non-destructive annotations already cover the safety profile, and the description adds useful behavioral context by naming the outputs: final stats, ability stats, armor mitigation, and mod capacity. It still omits assumptions and caveats such as default handling of conditionals or peak-stack behavior.

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?

The description is a single front-loaded sentence with no filler. Every clause contributes either scope or output information.

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 12-parameter calculation tool with no output schema, the description names the covered item classes and the main output categories, while the schema handles parameter details. It is nearly complete, though it could say more about the returned structure and calculation assumptions.

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%, and the 12 parameters including nested objects are fully documented in the input schema. The description itself adds no parameter-level detail beyond the general calculation purpose, so 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 has a specific verb (Calculate), a specific resource (build), and a clear scope (Warframe, companion, Archwing, Necramech) plus the main computed outputs. It does not explicitly differentiate this from the sibling suggest_warframe_build, which is also Warframe-build-oriented, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states what the tool calculates but gives no explicit when-to-use guidance, prerequisites, or comparison to alternatives such as suggest_warframe_build or weapon_build. An agent must infer that this is for final stat calculation rather than build suggestions.

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