Warframe MCP Server

Overview Schema Source Related Servers Discussions Admin

crafting_usage

Check if resources or components are used in crafting recipes. See all items that require them as ingredients to decide if safe to sell.

Instructions

Find all items that use one or more given resources or components as crafting ingredients. Answers 'what is this used for?' and 'is it safe to sell?'

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_names": "<item_names>"
    },
    "name": "crafting_usage"
  }
}

Input Schema

Name	Required	Description	Default
`item_names`	Yes	Resource or component name(s) (e.g. ['Neurodes', 'Argon Crystal', 'Ash Systems'])

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so the description bears full responsibility. It correctly implies a read-only operation (search) without side effects, but does not disclose potential rate limits, authentication needs, or behavior for invalid inputs.

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?

Three short, front-loaded sentences with zero waste. Every sentence adds essential information: purpose, use cases, and expected answers.

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?

Given the tool's simplicity and absence of output schema, the description covers the core functionality well. However, it lacks any hint about the return format or fields, which could help an agent parse results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter, but the description adds meaning beyond schema by explaining the semantic purpose of the results (answering usage and sell-safety questions).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verb+resource ('Find all items that use...as crafting ingredients') and clarifies it answers two distinct questions. This clearly distinguishes it from siblings like crafting_requirements (which answers the inverse).

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

Usage Guidelines4/5

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

The description provides clear context for when to use (to check item usage or sell safety) but does not explicitly contrast with sibling tools or give when-not-to-use guidance.

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