Skip to main content
Glama

Search Market Players

search_market_players
Read-only

Search the transfer list for players currently on sale using skill, position, price, and other filters to scout market candidates; returns public information only, with full details via a player lookup.

Instructions

Search the transfer list with players currently on sale. It does not returns skills, but only public information. Use to scout the market and get a glimpse of what could be a good player(s) based on the request made. More details of a single player can be received via tool get_auction.

filters keys (PascalCase): Min/Max + Age, Height, Salary, Price, Overall, Potential, Experience, GameShape, JumpShot, JumpRange, OutsideDefense, Handling, Driving, Passing, InsideShot, InsideDefense, Rebound, ShotBlock, FreeThrow; plus Country, Position, SecondPosition, Injury (Nothing|OnlyInjured|ExcludeInjured), OnNationalTeam. Level-valued filters (skills, Experience, GameShape) take names like Average, Strong, Prolific, Legendary. More than four skill bounds needs a supporter; eight is the maximum. order_by e.g. AuctionTime, Age, Salary, CurrentBid, Overall, Potential. Searches go at most 150 deep, up to 30 per page.

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_market_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
offsetNo
filtersNo
order_byNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true, so the safety profile is already covered. The description still adds real behavior beyond that: results omit skills and carry only public information, more than four skill bounds requires a supporter account, eight bounds is the maximum, and searches are limited to 150 deep at 30 per page. It does not describe the response shape or what an empty/truncated result looks like, keeping it at a solid 3.

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

Conciseness4/5

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

Front-loads purpose and the sibling alternative in the first three sentences, then switches to a compact reference block for filter keys and limits, which is the right structure for a filter-heavy tool. Minor waste and grammar slips ("does not returns", "could be a good player(s)") keep it from a 5, but the density is justified by the schema's total lack of field descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and for a five-parameter tool with 0% schema coverage the description supplies the filter vocabulary, value conventions, ordering options, and hard caps an agent needs to call it correctly. Nothing essential to forming a valid search is missing.

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

Parameters4/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 all parameter meaning, and it does much of that: it enumerates the full PascalCase filter key set, explains level-valued filters, gives order_by examples, and states the depth/page caps. It never directly maps limit, offset, or sort to those caps, leaving the caller to infer that limit is per-page size and offset is depth, so it is not quite complete.

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 and resource ("Search the transfer list with players currently on sale") and immediately scopes what it does not return ("It does not returns skills, but only public information"). It also points to get_auction for the per-player detail case, so an agent can distinguish it from sibling detail tools without opening a schema.

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?

Gives clear when-to-use framing ("Use to scout the market and get a glimpse of what could be a good player(s) based on the request made") and names the alternative for drill-down ("More details of a single player can be received via tool get_auction"). It does not state explicit exclusions or when not to use it, so it falls short of a 5.

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