Cavalera Forge MCP

Terminal sell prices

terminal_prices

Read-onlyIdempotent

Find the best trade terminals buying a mineral in refined or raw form, compare price per SCU from UEX, and check each listing's update time to choose where to sell.

Instructions

Best trade terminals buying a mineral (refined and raw forms), price per SCU, from UEX, with the update time.

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": {
      "mineral": "<mineral>"
    },
    "name": "terminal_prices"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`mineral`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds useful context beyond that: the upstream source (UEX) and that each result carries an update timestamp, which matters for judging data staleness. It says nothing about result ordering, pagination, or what happens when no terminals buy the mineral, so it does not reach 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, but the phrasing is a fragment with loose word order ('Best trade terminals buying a mineral...'), which costs a beat of parsing. The key output fields are front-loaded, which is good.

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?

With no output schema, the description does a decent job naming the returned fields (price per SCU, update time) and the data source. However, for a two-parameter tool with 0% schema coverage, leaving 'limit' unexplained and giving no ordering guarantee leaves a genuine gap for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the parameter burden. It only clarifies the 'mineral' input indirectly ('refined and raw forms'), and never explains 'limit' (default 5, max 20) or whether the mineral must be an exact name. Half the parameters remain opaque.

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 the resource (trade terminals buying a mineral), the returned fields (price per SCU), the data source (UEX) and freshness (update time), so an agent knows exactly what it gets. It does not explicitly contrast itself with nearby siblings like mineral_info or marketplace_search, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus marketplace_search, marketplace_find_items, or mineral_info, and no preconditions. The only implicit signal is 'best terminals buying a mineral', which an agent must infer as the selection criterion.

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

Deploy Server