Skip to main content
Glama

Get National Team Training History

get_national_team_training_history
Read-only

Retrieve squad skill changes from club training for players on a national team, newest first; restricted to that team's coaches and assistants.

Instructions

Squad skill changes from club training of players included in a National team, newest first. Works only for coaches/assistant of said national team, otherwise the request will fail.

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": {
      "team_id": "<team_id>"
    },
    "name": "get_national_team_training_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
team_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds genuinely new behavior: authorization requirements, the failure mode for unauthorized callers, and the newest-first ordering. It does not disclose pagination behavior or result volume, which would complete the picture.

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 the core subject front-loaded and the access restriction immediately following. There is no filler.

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-value explanation is unnecessary, and the description covers scope, ordering, and permissions adequately for a read-only history tool. Pagination semantics for limit/offset remain the one notable gap.

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% for all three parameters, so the description carries the full burden and explains none of them. team_id's meaning is only implied by the national-team framing, and limit/offset defaults and maximums are left entirely to convention.

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 verb and resource: squad skill changes derived from club training of players on a national team, ordered newest first. An agent can tell this is a national-team-scoped training history, though it never explicitly contrasts with the sibling get_team_training_history for club teams.

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?

It gives a real precondition -- only coaches/assistants of that national team may call it, otherwise the request fails -- which is useful gating. It does not state when to prefer this over get_team_training_history or get_player_training, so callers must infer the alternative from the national-team framing.

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