warframe-builds-mcp

Overview Schema Source Related Servers Discussions Admin

alecaframe_account

Read-only

Read a player's AlecaFrame account stats—platinum, ducats, endo, currencies, mastery rank, recent trades, and relics—using a public token from the Stats tab.

Instructions

Read the player's AlecaFrame stats: platinum, ducats, endo and other currencies, mastery rank, recorded trades and relics. It has no owned mods or gear. Needs a public token from AlecaFrame's Stats tab.

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

Input Schema

Name	Required	Description	Default
`recent_trades`	No	Trades to list, up to 100. Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.12.0Nov 3, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, so the safety profile is covered; the description adds value beyond that by disclosing the data's boundaries (no mods/gear) and an external auth dependency. It stops short of describing what happens when the token is missing or invalid, or how fresh the snapshot is, which would matter for a tool pulling third-party stats.

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 sentences: contents first, exclusion second, prerequisite last. Every sentence carries information an agent could act on, and there is no restatement of the tool name or filler.

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 correctly does the work of enumerating returned fields so the agent knows what to expect. The auth prerequisite is also captured. What is missing is error/failure behavior around the token and whether the stats are a live or cached snapshot, which for an external-data tool leaves a small residual gap.

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 single parameter is fully documented in-schema ("Trades to list, up to 100. Default 10."). The description mentions "recorded trades" as a category but adds no meaning about the paging/limit behavior beyond what the schema already states, so the baseline of 3 applies.

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?

States a specific verb and resource ("Read the player's AlecaFrame stats") and then enumerates the exact data returned: platinum, ducats, endo, other currencies, mastery rank, recorded trades, relics. It also pre-empts confusion by declaring the negative scope ("It has no owned mods or gear"), which steers an agent away from treating it as an inventory/lookup tool.

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?

The prerequisite ("Needs a public token from AlecaFrame's Stats tab") is genuinely useful call-time guidance, but it is an auth requirement rather than a when-to-use rule. Nothing tells the agent how this differs from get_profile or when to prefer alecaframe_account over that sibling, which is the obvious ambiguity given the shared "player profile" territory.

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