Skip to main content
Glama

Get Player

get_player
Read-only

Retrieve a BuzzerBeater player’s public profile, attributes, and potential; view skills only for players on your own team.

Instructions

Player page. Includes only public information (age, name, potential, game shape, DMI, etc) and skills only for your own players.

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

Input Schema

NameRequiredDescriptionDefault
player_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries real added weight: it discloses the visibility model (public fields only, skills restricted to your own players), which materially affects how an agent should interpret an incomplete response. It stops short of covering failure behavior for unknown player_ids, but the data-scoping disclosure is genuinely useful context beyond the annotation.

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?

Two short sentences with the visibility constraint front-loaded and no filler. The trailing "etc" is mildly sloppy but does not obscure meaning.

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?

The tool is simple (one required parameter) and an output schema exists, so return values need not be documented. The description covers the one non-obvious aspect, conditional field visibility; only the player_id format and error behavior are unaddressed.

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 description coverage is 0% and the single parameter player_id has no schema description. The description adds nothing about its format or provenance, so the agent must guess whether it is a numeric ID, slug, or opaque string and where to obtain one.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with the noun phrase "Player page" rather than a verb+resource, though combined with the name get_player the intent (retrieve a player's profile) is inferable. It specifies contents well (age, name, potential, game shape, DMI, skills) but never states how this differs from siblings like get_team_roster, scout_team, or search_market_players.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no named alternative, and no suggestion of where a player_id comes from (e.g., a search or roster tool). Usage is only implied by the required player_id parameter.

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