Skip to main content
Glama

Search marketplace listings

search_listings
Read-onlyIdempotent

Find player listings on the UEX marketplace with filters for item, quality, age, price, system, location, seller, category, and text; rank results by quality, recency, or price with direct links.

Instructions

Find player listings on the UEX marketplace with combined filters (item, quality range, age, price, system, location, seller, title words, category), ranked by quality, recency or price. Each result has a direct link to the listing.

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

Input Schema

NameRequiredDescriptionDefault
itemNoItem name, e.g. 'Stileron', 'Quantainium', 'Pembroke helmet'. Leave empty to search recent listings by text/category.
sortNoquality: best first; recent: newest first; price: cheapest first.quality
textNoWords that must all appear in the listing title.
limitNo
sellerNoSubstring of the seller's username.
systemNoStar system, e.g. 'Stanton', 'Pyro', 'Nyx'.
categoryNoUEX category or section, e.g. 'Commodities', 'Helmets', 'Armor', 'Personal Weapons', 'Quantum Drives'.
id_itemsNoExact UEX item ids (from find_items or an 'ambiguous' answer). Overrides `item`. Up to 6.
locationNoSubstring of the location, e.g. 'Area18'.
operationNo'sell': players selling (you want to buy). 'buy': players looking to buy (you want to sell).sell
price_maxNoMaximum price, in the listing's own unit (see `unit`).
quality_maxNo
quality_minNoMinimum quality 0-1000. Listings of unknown quality are excluded when set.
max_age_daysNoOnly listings posted within this many days. 0 or empty: any age. 'Recent' usually means 7 to 14.
one_per_sellerNoKeep only each seller's best listing (default), otherwise one prolific seller fills the whole list.
include_unknown_qualityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that results are ranked and that each carries a direct listing link, which is useful return context, but with no output schema it says nothing about result fields, pagination, or how the default one_per_seller collapse affects the result set.

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?

Two tight sentences: purpose and filters first, ranking and return shape second. No filler and nothing redundant in structure.

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 16-parameter, all-optional search tool with annotations covering safety and a rich schema, the description gives enough to call it correctly. The gaps (no mention of the limit cap, default age window, or one-per-seller behavior) are minor because the schema documents them.

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 81%, so nearly every parameter is already documented with examples and semantics. The description's filter list mostly restates what the schema already says and adds no syntax or interaction details (e.g. how quality range interacts with include_unknown_quality), so baseline 3 applies.

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 a specific verb and resource (find player listings on the UEX marketplace) and enumerates the filter dimensions and sort modes, which lets an agent distinguish it from find_items and marketplace_status. It stops short of explicitly naming those siblings as alternatives, so it is clear but not fully differentiated.

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?

Usage is implied by the filter list (search listings when you have item/quality/price/location criteria), but there is no explicit 'use this instead of X' guidance in the description itself. The only routing hint, find_items for item ids, lives in the schema's id_items description rather than the tool description.

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

Deploy Server

Other Tools