Skip to main content
Glama

animate_drill

Create one animated practice with player movements and ball paths, saved to the coach's account. Use it when the coach wants to see a single practice move, for example "Make a practice with a diagram for 1v1 defending". The answer gives the picture and the animated practice link on their own labelled lines.

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": {
      "description": "<description>"
    },
    "name": "animate_drill"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoPractice category (e.g. "passing", "shooting", "tactical")
age_groupNoAge group (e.g. "u10", "u14", "senior")
descriptionYesDescribe the practice you want animated
retry_operation_idNoFailed operation ID to retry explicitly with the same practice request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Drill category (e.g. \"passing\", \"shooting\", \"tactical\")"New value: +"Practice category (e.g. \"passing\", \"shooting\", \"tactical\")"
    • changedInput schema / properties / description / description
      Previous value: -"Describe the drill you want animated"New value: +"Describe the practice you want animated"
    • changedInput schema / properties / retry_operation_id / description
      Previous value: -"Failed operation ID to retry explicitly with the same drill request"New value: +"Failed operation ID to retry explicitly with the same practice request"
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already cover the write, non-idempotent, non-destructive profile. The description adds real value by disclosing persistence ('saved to the coach's account') and the return shape ('the picture and the animated practice link on their own labelled lines'), but says nothing about cost/credits consumption or what retry_operation_id implies for failed generations.

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?

Three front-loaded sentences: purpose, trigger with example, and output format. Every sentence carries information; the only minor looseness is the parenthetical example, which is still justified as a routing cue.

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 four-parameter generation tool with full schema coverage and no output schema, the definition covers purpose, trigger, persistence, and return format. The one gap is retry behavior for failed operations, which appears in the schema but is never explained in the description.

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 100%, so each of the four parameters is already documented in the schema, setting the baseline at 3. The description's example request illustrates the description parameter but adds no new semantics for category, age_group, or retry_operation_id.

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?

States a specific verb and resource: 'Create one animated practice with player movements and ball paths, saved to the coach's account.' The emphasis on 'one'/'single practice move' implicitly separates it from session-level siblings like generate_session_plan, so the agent can route correctly 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 Guidelines4/5

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

Gives a clear usage trigger ('Use it when the coach wants to see a single practice move') plus a concrete example request. It stops short of explicit exclusions or naming the alternative for multi-drill or plan-level requests, which is why it is not a 5.

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.

Resources