Skip to main content
Glama

Get Team Training History

get_team_training_history
Read-only

Retrieve a team's past training sessions and skill upgrades with sorting and pagination; non-supporters get only the latest session.

Instructions

Results of past training sessions (skill upgrades and such) of your own team. Non-supporters get the latest session only.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
offsetNo
team_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 the interesting behavior: it discloses an access-tier-dependent truncation ('Non-supporters get the latest session only'), which materially affects how results should be interpreted. It stops short of covering paging or ordering behavior, but that is largely a parameter concern.

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 core scope front-loaded and no repetition. The parenthetical '(skill upgrades and such)' is vague filler that could be tightened, but it costs little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return values are covered by the output schema, so the description need not explain them, and the access-tier note is a useful addition. However, for a tool with four fully undocumented, un-enumerated parameters, the description should say something about ordering and paging to be complete.

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% across four parameters, and the description explains none of them — sort direction, limit, offset, and team_id are all left to inference. Only a weak hint about team ownership ('your own team') touches team_id; pagination semantics are entirely undocumented.

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 ('Results of past training sessions') and scopes it to 'your own team', which lets an agent distinguish it from get_national_team_training_history and from get_team_training. It does not explicitly name those siblings, but the ownership and past-tense framing make the target clear.

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 statement of when to call this versus get_team_training (current training) or the national-team variant; the agent must infer the distinction from the word 'past'. The sentence about non-supporters is a behavioral constraint, not usage guidance.

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