Skip to main content
Glama

List players

aura_list_players
Read-onlyIdempotent

Player profiles for a whole sport, a page at a time. For one team use aura_get_team_roster.

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": {
      "sport": "<sport>"
    },
    "name": "aura_list_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportYes
cursorNopage.nextCursor from the previous call
pageSizeNoDefaults to 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"page.next from the previous call"New value: +"page.nextCursor from the previous call"
    • addedInput schema / properties / pageSize
      Added value: +{
      +  "description": "Defaults to 100",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "number"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive), so the description only needs to add context. It does so by disclosing pagination behavior ("a page at a time"), which is meaningful because there is no output schema to reveal the cursor loop. It does not state whether results cover all historical or only current players, which limits it slightly.

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 short sentences with zero filler. The scope statement is front-loaded and the sibling redirect follows immediately, so an agent reads the routing rule before it starts reasoning about parameters.

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 three-parameter read-only list tool with no output schema, the description covers what is returned (player profiles), the scope (per sport), and the paginated nature of the results. Only minor gaps remain, such as what fields a profile contains or whether inactive athletes are included.

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 67%, with cursor and pageSize already documented in the schema (cursor references page.nextCursor, pageSize states the default). The description's phrase "whole sport" reinforces the meaning of the required sport parameter but adds nothing about the enum values or page-size limits, so it sits at the baseline.

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?

"Player profiles for a whole sport, a page at a time" gives a specific resource (player profiles), a scope (whole sport, not a team), and a delivery mode (paginated). An agent can immediately distinguish this from aura_get_team_roster and aura_get_player 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?

It explicitly routes the agent to the sibling tool for the common alternative case ("For one team use aura_get_team_roster"), which is real when-to-use guidance. It stops short of distinguishing this from aura_get_player for single-athlete lookups or explaining when paginated enumeration is preferable to targeted lookups, so it is clear but not fully exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.