Skip to main content
Glama
Sign In

PocketCaddie

by io.pocketcaddie
OverviewDiscussionsAdmin

Practice goals

goals
Read-onlyIdempotent

Use this when a linked golfer asks about their goals, what they're working on, their focus, or how a block of practice went: the active focus goal (the reading, its zone, who set it, the block so far and the before), the long-term goal, goals waiting in the app, and recent goals with the app's outcome (Improved, Held, Not yet, Mastered). Counts are focus swings in the zone out of focus swings with a read. Only call a change real when the outcome says so.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "goals"
  }
}

Input Schema

NameRequiredDescriptionDefault
recentNoHow many finished goals to include.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover read-only and non-destructive behavior, and the description adds substantial context beyond them: it requires a linked golfer, explains what is included in the active focus goal, defines how counts are calculated, lists possible outcomes, and warns that a change should only be treated as real when the outcome says so.

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?

The description is front-loaded with the usage trigger and then lists the returned data. It is dense but mostly free of filler, though the first sentence is long and carries several nested clauses that could be easier to scan.

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

Completeness5/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 carries the burden of explaining return contents and does so thoroughly: active focus goal, long-term goal, waiting goals, recent goals with outcomes, count semantics, and interpretation guidance. Combined with annotations and the fully documented single parameter, an agent has enough context to call it correctly.

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?

There is only one optional parameter, and schema description coverage is 100%, so the schema already fully documents it. The description does not mention the 'recent' parameter or explain how its value affects the response, so it adds no parameter-level meaning.

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 retrieval purpose: when a linked golfer asks about goals, focus, or practice blocks. It enumerates the exact goal-related data returned, making the resource clear without explicitly differentiating from siblings such as progress or 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?

It gives clear triggering conditions: linked golfer questions about goals, current focus, or how a practice block went. It does not provide explicit when-not conditions or name alternative sibling tools for overlapping queries.

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