Cavalera Forge MCP

Find marketplace items

marketplace_find_items

Read-onlyIdempotent

Look up UEX catalog items by partial name to retrieve exact item names and IDs for marketplace_search queries.

Instructions

Look up items in the UEX catalog (all items, not only crafting) to get exact names and ids for marketplace_search.

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": {
      "query": "<query>"
    },
    "name": "marketplace_find_items"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	Yes	Part of an item name.
`category`	No	Optional UEX category or section.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is fully covered. The description adds the catalog-scope nuance ('all items, not only crafting'), but says nothing about result limits, pagination, or how many matches come back by default.

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?

A single sentence with no filler; the scope qualifier and the intended follow-up tool are both front-loaded where an agent will see them first.

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?

For a simple three-parameter read-only lookup with no output schema, the description covers purpose, scope, and downstream use, and hints at the return content (names and ids). Adding the default/maximum result count would close the remaining 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 coverage is 67% — query and category are documented inline, while limit (default 10, max 30) is not. The description adds no parameter-level guidance such as how to match partial names or how category filters results, so it neither compensates for nor compounds the moderate gap.

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 (look up) and resource (items in the UEX catalog), and explicitly disambiguates scope with 'all items, not only crafting.' It also names the downstream consumer, marketplace_search, so an agent can place it relative to siblings like search_products or craftable_from.

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 makes the usage pattern clear: use this to resolve exact names and ids before calling marketplace_search. It doesn't state explicit exclusions (e.g., when to prefer search_products or category browsing instead), so it stops short of a full when/when-not guide.

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

Deploy Server