Skip to main content
Glama

Get Auction

get_auction
Read-only

Retrieves complete auction details for a listed BuzzerBeater player, including skills, so you can evaluate and compare them with your current team. Filter with search_market_players first.

Instructions

Auction of a listed player. Includes more details then what received with search_market_players, including player skills. Use it when the user asks for a player on sale and to compare it with the current people in team. Avoid to abuse of this call for crawling for players. Better filter with search_market_players first in case.

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": {
      "player_id": "<player_id>"
    },
    "name": "get_auction"
  }
}

Input Schema

NameRequiredDescriptionDefault
player_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint=true already establishes this as a safe read, so the description only needs to add behavior beyond that. It usefully discloses that results are richer than the search listing (includes player skills) and warns about abusive crawling, but says nothing about what happens when the player has no active auction or about response shape (covered by the output schema).

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?

Three short sentences with the purpose front-loaded and no filler. Grammar is rough ('more details then what received', 'Avoid to abuse of this call') and the last two sentences partially overlap on the search-first advice.

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 single-parameter read tool with an output schema and safety annotations already in place, the description covers purpose, differentiation, and rate-limit etiquette. The only real gap is the ambiguous meaning of player_id and the not-found/unlisted case.

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?

There is one parameter with 0% schema description coverage, so the description must carry the load. 'Auction of a listed player' implies player_id identifies the player, but it never clarifies whether the ID is a player ID versus an auction/listing ID, nor what happens for unlisted players.

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 states a specific resource (the auction of a listed player) and explicitly contrasts its content with search_market_players by noting it includes player skills. The verb is only implied via the tool name rather than stated outright, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete trigger ('when the user asks for a player on sale and to compare it with the current people in team'), a named alternative (search_market_players), and an explicit caution against crawling. Both when-to-use and when-to-avoid are covered.

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