Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get drill digest

get_drill_digest
Read-onlyIdempotent

Read the reviewed summary of one improvement area: the ideas coaches repeat, the real number of distinct channels behind each, and one clip per idea. Use it for an overview before choosing clips; for more clips use search_drill_clips. Null until a reviewed summary exists. Read-only.

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": {
      "area": "<area>"
    },
    "name": "get_drill_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYesImprovement area id, as listed by list_drill_areas: slice, putt, bunker, driver…
langNoLanguage of titles and steps: es, en, fr, de, it, pt, nl, sv, da, fi, no or ja. Default es; pass the player's language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / area / description
      Added value: +"Improvement area id, as listed by list_drill_areas: slice, putt, bunker, driver…"
    • addedInput schema / properties / lang / description
      Added value: +"Language of titles and steps: es, en, fr, de, it, pt, nl, sv, da, fi, no or ja. Default es; pass the player's language."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so 'Read-only' in the description is reinforcing rather than new. The genuinely additive behavior is 'Null until a reviewed summary exists', which tells the agent how to interpret an empty response — a real failure mode it would otherwise misread. Content composition (one clip per idea, real distinct-channel counts) further describes what the payload looks like beyond what annotations convey.

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?

Three short sentences, each carrying distinct information: what, when/alternative, and the null caveat. The most decision-relevant content (what it returns and when to pick it) is front-loaded.

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?

No output schema exists, so the description does the work of describing the return payload — ideas, distinct-channel counts, one clip per idea — plus the null case, which is enough to call and interpret the tool. The precise shape of the returned object (field names, ordering) is not described, a minor omission for an overview tool.

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 both parameters are enums with descriptions, including the pointer to list_drill_areas and the default for lang. The description only implies the single-area scoping already spelled out in the schema, so it adds no format or selection detail beyond structured fields — baseline 3.

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?

Opens with a specific verb and resource ('Read the reviewed summary of one improvement area') and immediately enumerates what that summary contains: repeated ideas, distinct channel counts, one clip per idea. An agent can distinguish it from get_drill_clip, get_drills, and search_drill_clips without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

States the intended role ('overview before choosing clips') and names the alternative for the other job ('for more clips use search_drill_clips'), so the routing decision is explicit. The prerequisite that a reviewed summary must exist is also called out.

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