Cavalera Forge MCP

Search marketplace listings

marketplace_search

Read-onlyIdempotent

Search UEX player marketplace listings by item, category, seller, system, location, price, quality, and age; sort by quality, recency, or price and get one result per seller with a direct link.

Instructions

UEX player marketplace listings with combined filters, ranked by quality, recency or price, one per seller, each with a direct link. Qualities read from titles are marked '~', defaults '500?'.

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

Input Schema

Name	Required	Description	Default
`item`	No	Item name, e.g. 'Stileron', 'Quantainium', 'Pembroke helmet'. Leave empty to search recent listings by text/category.
`sort`	No	quality: best first; recent: newest first; price: cheapest first.	quality
`text`	No	Words that must all appear in the title.
`limit`	No
`seller`	No	Substring of the seller's username.
`system`	No	Star system, e.g. 'Stanton', 'Pyro', 'Nyx'.
`category`	No	UEX category or section, e.g. 'Helmets'.
`id_items`	No	Exact UEX item ids (from marketplace_find_items or an 'ambiguous' answer). Up to 6.
`location`	No	Substring of the location.
`operation`	No	'sell': players selling (you want to buy). 'buy': players looking to buy.	sell
`price_max`	No	Maximum price in the listing's own unit.
`quality_max`	No
`quality_min`	No	Minimum quality 0-1000; listings of unknown quality are excluded when set.
`max_age_days`	No	Posted within this many days; 0 or empty: any age. 'Recent' usually means 7 to 14.
`one_per_seller`	No
`include_unknown_quality`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already establish the safe read-only, idempotent, non-destructive profile. The description adds useful behavioral context beyond annotations: one result per seller by default, direct links, and special notation for qualities parsed from titles, including a default marker. It does not cover rate limits or result formatting in depth, but it adds meaningful operational detail.

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?

The description is two compact sentences with no wasted text, and the core purpose and ranking behavior are front-loaded. The second sentence adds specific caveats about quality markers without bloating the definition.

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 has 16 optional parameters and no output schema, so the description carries some burden for explaining result shape and behavior. It mentions direct links, one-per-seller, ranking, and quality markers, but does not fully describe return structure or how combined filters interact. Given the rich schema coverage, this is adequate but not complete.

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 75%, so most parameter meaning is already documented in the schema. The description adds useful context for sorting, one-per-seller behavior, and quality markers/defaults, but with 16 parameters it does not compensate for every gap, such as the undocumented quality_max and include_unknown_quality parameters.

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 clearly identifies the resource as UEX player marketplace listings with combined filters and ranked results. It specifies ranking modes and one-per-seller behavior, making the tool's core purpose understandable, though it does not explicitly contrast itself with siblings like marketplace_find_items or terminal_prices.

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?

The description explains what the tool returns but gives no explicit guidance on when to use it instead of sibling tools. There is no mention of prerequisites, exclusions, or alternative tools for similar marketplace/item searches.

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

Deploy Server