Skip to main content
Glama
warframe-builds-mcp

warframe-builds-mcp

by pregamer189

update_profile

Idempotent

Update a Warframe player's saved profile with owned and missing mods/items, notes, rivens, spare items, and mods mode so build suggestions match their collection.

Instructions

Change the player's saved profile. Tell the player what you changed. Use mods_mode owned_only only once owned_mods is complete, because suggestions then use nothing else.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoReplaces the player's free-form notes, such as playstyle or goals.
rivensNoRivens by weapon, as {weapon: {effects, polarity, drain}}. null removes one. Pass one to weapon tools as riven.
mods_modeNoassume_all: has every mod except missing_mods. owned_only: has only owned_mods.
spare_itemsNoSpare tradable items to sell, as {name: count}. A count of 0 removes one. Used by sell_advice.
add_owned_modsNo
add_owned_itemsNoWarframes and weapons the player has.
add_missing_modsNo
remove_owned_modsNo
remove_owned_itemsNo
remove_missing_modsNo
alecaframe_public_tokenNoA public token from AlecaFrame's Stats tab. An empty value removes it. It is kept in the profile file and never shown again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, so the safety profile is covered. The description adds the useful dependency that suggestions draw exclusively from owned_mods under owned_only, but is silent on merge semantics (partial updates, add vs. remove interaction) and on what happens to unspecified fields.

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?

Three short sentences with the core action front-loaded and no filler. The final clause ('because suggestions then use nothing else') is terse to the point of ambiguity but still earns its place as a rationale.

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 an 11-parameter mutation tool with nested objects and no output schema, the description is thin on update semantics and conflict behavior. It covers the mods_mode case but leaves an agent unsure how add/remove arrays and the notes replacement interact.

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 coverage is 55%, with several array parameters (add_owned_mods, add_owned_items, add_missing_mods and their remove counterparts) undocumented. The description clarifies the mods_mode/owned_mods coupling, which is genuinely useful, but doesn't compensate for the remaining undocumented parameters.

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: change the player's saved profile. Combined with the sibling get_profile, the read/write split is inferable, though the description never names get_profile to make the contrast explicit.

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?

Gives one concrete conditional rule (use mods_mode owned_only only after owned_mods is complete) and an instruction to report changes to the player. It offers no guidance on when to prefer this over adjacent tools like save_build or when not to call it.

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