Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get drills

get_drills
Read-onlyIdempotent

List the scorable practice drills: short game, long game or putting tests where each attempt is one number against a target, with title, goal, steps and how it scores. Only golf drills of Badgie's global set and of the player's school, if any: anything not listed is not a drill of the method, so never invent one. Use it when the player wants a scored test or names a drill of the app; log attempts with log_drill_attempt and plan them with save_practice_plan. For video clips use search_drill_clips. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoOnly one area: short_game, long_game or putting. Leave it out when looking for a drill by name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Área a filtrar: 'short_game', 'long_game' o 'putting'."New value: +"Only one area: short_game, long_game or putting. Leave it out when looking for a drill by name."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the catalog scope: only Badgie's global set and the player's school, with an explicit warning not to invent drills outside that set. It also previews returned fields such as title, goal, steps, and scoring, which helps an agent understand what the tool provides. It does not discuss pagination or ordering, but the annotations already cover safety and idempotence.

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 core definition, followed by scope, usage, routing, and safety. It is somewhat long for a one-parameter list tool, and the final 'Read-only' sentence repeats annotation information, but most sentences contribute useful context.

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 simple read-only list tool with one optional parameter and no output schema, the description is largely complete: it explains what a drill is, what is included, what fields are returned, and when to use related tools. Only minor details such as result ordering or pagination are absent.

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 100%, and the schema already explains the single optional category parameter, including allowed values and the instruction to omit it when searching by name. The description reinforces that drills are short game, long game, or putting, but adds no syntax or filtering detail beyond what the schema provides.

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?

The description gives a specific verb and resource ('List the scorable practice drills') and defines the drill type precisely: short game, long game, or putting tests scored as one number against a target. It also distinguishes these drills from video clips by naming search_drill_clips, so an agent can separate get_drills from nearby sibling tools.

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 states clear when-to-use guidance: use when the player wants a scored test or names a drill of the app, and it names alternatives for logging, planning, and video clips. The main gap is that two referenced tools, log_drill_attempt and save_practice_plan, do not appear in the supplied sibling list, which could confuse routing despite the otherwise strong guidance.

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

All Morris Golf 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