warframe-builds-mcp

Overview Schema Source Related Servers Discussions Admin

sell_advice

Read-only

Rank spare Warframe items by recent market price and demand, and flag mods used by saved builds so you know what to sell and what to keep.

Instructions

Rank items to sell by recent price and demand on warframe.market, and warn about mods saved builds use. Checks the profile's spare_items unless you pass items. Advice for trading in the game.

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": "sell_advice"
  }
}

Input Schema

Name	Required	Description	Default
`items`	No	Up to 25 names or {name, count, rank, subtype} objects. Mods and arcanes default to rank 0. Defaults to spare_items.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.12.0Nov 3, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, openWorldHint and a non-idempotent hint; the description usefully confirms the external warframe.market dependency and the spare_items default. However, it does not explain why the call is non-idempotent (live market data) or what a warning looks like, so it only adds modest context beyond the annotations.

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, front-loaded with the core ranking behavior and the default-source rule. The closing line 'Advice for trading in the game' is filler that could be cut, but overall there is little waste.

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?

The tool is a single-optional-parameter read whose safety profile is fully covered by annotations, and the description explains the data source and ranking basis. With no output schema, though, it never sketches the shape of the result (per-item price, demand signal, warning entries), leaving the agent guessing at what it gets back.

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 100% and the schema itself already states the 'Up to 25 names or {name, count, rank, subtype} objects' format and the spare_items default. The description's mention of the same default adds no meaning beyond the structured field, so the baseline 3 applies.

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 states a specific verb and resource: rank items to sell by recent price and demand on warframe.market, plus a secondary behavior (warning about mods used in saved builds). This is clearly distinguishable from price-lookup siblings like market_price, though it never names the sibling it is not.

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 is only implied: 'Advice for trading in the game' plus the note that it reads spare_items unless items are passed. There is no explicit statement of when to prefer this over market_price or how it relates to get_profile/weapon_build for the saved-build warning.

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