Skip to main content
Glama

Get Player Training

get_player_training
Read-only

Retrieve training sessions for one of your own players, with optional sort order. Requires a supporter subscription; otherwise no training data is returned.

Instructions

Training sessions of your own player. Require a supporter subscription, or info won't be returned to you.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
player_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds a genuinely valuable operational fact: a supporter subscription is required or no info is returned, warning the agent about a silent empty response. It stops short of describing pagination, sorting behavior, or volume of sessions, so it is not fully transparent.

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 no filler, and the resource scoping is front-loaded ahead of the access precondition. Nothing is repeated from the title or annotations.

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?

With an output schema present, return values need no explanation, and the subscription prerequisite is the key call-blocking detail, which is covered. The only gap is the sort parameter's meaning and default, which leaves the agent guessing about ordering.

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 0% for two parameters, so the description must compensate and does so only partially: 'your own player' clarifies that player_id refers to the caller's own player. The 'sort' parameter (Asc/Desc, default null) is left entirely undocumented in both schema and description.

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 names a specific resource (training sessions) and scopes it to 'your own player', which separates it from the team- and national-team-training siblings. It lacks an explicit verb, relying on the tool name to convey retrieval, but an agent can tell what data comes back without opening the schema.

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

Usage Guidelines3/5

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

The phrase 'your own player' implicitly tells the agent this tool is for one's own player rather than arbitrary players or teams, which is useful routing context. However, no sibling is named and there is no explicit when-not guidance, so the agent must infer the boundary against get_team_training and get_player on its own.

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