warframe-builds-mcp

Overview Schema Source Related Servers Discussions Admin

market_price

Read-only

Look up live Warframe.market platinum prices and recent sales for items, sets, mods, arcanes, or relics, with optional rank and subtype filters.

Instructions

Look up an item's live price and recent sales on warframe.market, in platinum. Sets have names such as Saryn Prime Set.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item": "<item>"
    },
    "name": "market_price"
  }
}

Input Schema

Name	Required	Description
`item`	Yes
`rank`	No	Rank to price, for mods and arcanes. Default 0, as ranks are never mixed.
`subtype`	No	A variant such as a relic's radiant. Defaults to the first listed.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.12.0Nov 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-network behavior are covered. The description still adds real value beyond them: it identifies the data source (warframe.market), the currency (platinum), the data shape (live price plus recent sales), and explains why the call is non-idempotent, since prices are live. It omits any note on rate limits, caching, or auth, which keeps it from a 5.

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 short sentences with no filler, and the core purpose is front-loaded before the naming hint. Every clause carries information the agent needs.

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?

With no output schema, the description does a reasonable job of sketching the return content (live price and recent sales in platinum). For a read-only lookup tool that is nearly complete; the remaining gap is error or empty-result behavior for unrecognized item names.

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 67%: rank and subtype are documented in the schema, but the required 'item' parameter has no schema description. The description partially compensates by giving a naming convention example ('Saryn Prime Set'), which is genuinely useful for constructing a valid item string, but it gives no format guidance for individual parts versus sets or for item-name casing beyond that single example.

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 names a specific verb and resource: looking up an item's live price and recent sales on warframe.market, denominated in platinum. That is far more concrete than the bare name 'market_price'. It stops short of differentiating itself from the closest sibling, sell_advice, which an agent could plausibly confuse with pricing lookup.

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: an agent infers it should call this when it needs a price. There is no statement of when not to use it, no mention of sell_advice as the alternative for pricing strategy, and no note on what to do when an item is unknown or not tradeable.

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