Skip to main content
Glama

mmo_unified_market_search

Search across multiple MMO marketplaces at once and compare prices across games. Returns normalized results for items from WoW, FFXIV, EVE, OSRS, PoE, and Diablo.

Instructions

Search across ALL supported MMO marketplaces simultaneously. WoW Auction House, FFXIV Market Board, EVE Market, OSRS Grand Exchange, PoE Trade, Diablo Trade. Returns normalized results with cross-game price comparisons.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_nameYesItem name to search across all games
gamesNoGames to search (default: all)
realmNoRealm/world/server name (game-specific)
limit_per_gameNo
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It states 'Returns normalized results with cross-game price comparisons' and indicates simultaneous search across games. However, it does not cover authentication, rate limits, error handling, or performance characteristics.

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 sentences, no wasted words. The first sentence states the action and scope, the second lists supported games and output type. Front-loaded with key information.

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?

Given 4 parameters and no output schema, the description covers the main purpose and output but lacks details on parameter usage (e.g., realm interaction, limit behavior) and normalization specifics. It is minimally complete for a search tool but could be richer.

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 coverage is 75% (3 of 4 params have descriptions), and the description adds no additional meaning for parameters beyond what the schema already provides. It does not explain the 'realm' or 'limit_per_game' parameters, or how the 'games' filter default works.

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?

The description uses a specific verb 'Search' and a clear resource 'ALL supported MMO marketplaces simultaneously', listing six specific games. This distinguishes it from sibling tools like dashboards or conversions.

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 clearly indicates when to use this tool: for multi-game market searches with cross-game price comparison. It implies coverage of all listed games but does not explicitly state when not to use it or mention alternatives for single-game searches.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/mmoagent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server