Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

List drill areas

list_drill_areas
Read-onlyIdempotent

List the improvement areas of Morris's drill library (short clips cut from other coaches' YouTube lessons and curated by Morris) with how many videos, clips and channels each has, and the area of the player's latest swing analysis. Call it first to pick an area for search_drill_clips or get_drill_digest. 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": "list_drill_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Changed1 schema field changed
    • 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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the 'Read-only' sentence is largely redundant. However, the description adds genuinely non-obvious behavior: that a list tool also surfaces the area of the player's latest swing analysis, and it defines the aggregate counts returned per area. It omits ordering, empty-library behavior and result size.

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?

Two sentences, front-loaded with the resource and its payload, followed by the routing advice. The trailing 'Read-only.' duplicates the annotations and adds no information, a minor waste.

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?

With no output schema, the description carries the burden of describing returns, and it does so well by naming the per-area counts and the latest swing analysis area. It falls short only on ordering, whether areas can be empty, and the meaning of the single lang parameter.

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?

Only one optional parameter (lang) and schema description coverage is 100%, so the baseline is 3. The description never mentions language selection, so nothing is added beyond the enum's own documentation of default es and passing the player's language.

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?

States a specific verb and resource (list the drill library's improvement areas) and enumerates what each entry carries: video, clip and channel counts plus the area of the player's latest swing analysis. That scope is clearly distinct from siblings like search_drill_clips or get_drills.

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?

Explicitly instructs 'Call it first to pick an area for search_drill_clips or get_drill_digest', naming the follow-up tools and the precondition that selects them. The agent knows both when to call this and what to call next.

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