Skip to main content
Glama

Get Team Training

get_team_training
Read-only

Fetch your team's current training drill and player positions by team ID to review training focus and assignments.

Instructions

Current training drill and positions of your own team.

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

Input Schema

NameRequiredDescriptionDefault
team_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a non-destructive read, so the description's burden is reduced. It adds the useful qualifier that the result is a current snapshot for 'your own team', but says nothing about ownership validation, failure behavior if team_id isn't yours, or freshness of the data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, but the brevity comes from under-specification rather than precision. It is front-loaded and readable, yet lacks the structure (scope, distinguishing detail) a tool definition of this kind warrants.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, and the readOnly annotation covers the safety profile. Still, for a tool whose only parameter is undocumented, the description leaves gaps: what 'positions' means, whether the team is implicit or must match team_id, and how the data differs from the training-history siblings.

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 the single required parameter team_id, so the description must compensate and it barely does. 'Your own team' implies a constraint on which id is acceptable but gives no format, source, or example of a valid team_id.

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 names the resource being returned (current training drill and positions of a team), and the word 'Current' distinguishes it from the history siblings. However, it is a noun fragment rather than a clear verb+resource statement, and terms like 'positions' and 'training drill' are domain jargon an agent may not resolve without opening the output schema.

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 when-to-use guidance, no stated prerequisites, and no pointer to the history variants. The only implicit scoping cue is 'your own team', which hints that team_id should be the caller's team but never states the rule or what happens otherwise.

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