Skip to main content
Glama
Sign In

PocketCaddie

by io.pocketcaddie
OverviewDiscussionsAdmin

Build a practice plan

practice_plan
Read-onlyIdempotent

Use this when a golfer asks for a practice plan, a range routine or a session to do at home, e.g. 'build me a 30-minute range plan', 'what should I do with a bucket of balls', 'home practice for tempo'. Builds a timed plan from PocketCaddie drills for 1–3 skills (map their goal to the closest skills). If the golfer has linked their account, call progress first and pass their lowest-scoring skills.

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": {
      "skills": "<skills>"
    },
    "name": "practice_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
whereNorange
skillsYes
minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety and idempotency, while the description adds useful behavioral context: plans are built from PocketCaddie drills, limited to 1–3 skills, and should use progress data for linked accounts. It does not describe the returned plan format, but the safety profile is already covered.

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?

The description is compact and front-loaded with the triggering use cases, followed by construction details and the progress prerequisite. The examples are relevant and no sentence feels wasted.

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 read-only planning tool with annotations and no output schema, the description is mostly complete: it explains what is generated, input skill mapping, and the progress dependency. Minor gaps remain around return structure and full parameter semantics.

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 coverage is 0%, so the description must carry parameter meaning. It clarifies that skills should be mapped to the closest 1–3 skills and gives examples implying range/home and 30-minute plans, but it does not fully define all three parameters, including the 'any' location option and minutes constraints.

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?

States a specific action and artifact: builds a timed practice plan from PocketCaddie drills for 1–3 skills. The examples clarify intent, but the description does not explicitly distinguish this from sibling tools such as coach_plan.

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 clear triggering situations and example user requests, plus a prerequisite to call progress first when the account is linked. It does not state when not to use this tool or name alternative siblings besides progress.

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

All PocketCaddie toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources