Skip to main content
Glama

plan_player_development

Build a development plan for one player: what to work on, practices to help, and how to check progress.

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": {
      "notes": "<notes>"
    },
    "name": "plan_player_development"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesYesWhat you have seen from the player: what they do well and what they find hard
positionNoWhere they play, for example centre-back or winger (optional)
age_groupNoAge group, for example U10 or U14 (optional)
player_nameNoFirst name for the plan heading (optional). It stays in this reply and is not saved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the generated plan is persisted, where it goes, or that the player's name is discarded after the reply — a notable gap for a non-read-only tool.

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?

A single front-loaded sentence with no filler, and the colon-list structure quickly conveys the plan's three outputs. It is efficient, though slightly thin for a generative tool.

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?

With no output schema, the description should carry more of the burden of describing what comes back and whether the result is saved; it only sketches the plan's three sections. Four well-documented parameters compensate somewhat, making it adequate but not complete.

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%, with each of the four parameters documented in the schema itself (including the note that player_name is not saved). The description adds no syntax, format, or quality guidance for the required 'notes' field, so baseline 3 applies.

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 gives a specific verb and resource ('Build a development plan for one player') and even names the plan's three components: focus areas, practices, and progress checks. It is clear on its own, but it never distinguishes itself from the sibling generate_session_plan, so an agent must infer the long-term vs. single-session split.

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 when-to-use guidance, no prerequisites, and no mention of when a different tool (e.g., generate_session_plan or get_coaching_advice) would be the better choice. Usage is only implied by the word 'development plan' versus a session plan.

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