Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Search drill clips

search_drill_clips
Read-onlyIdempotent

List clips of one improvement area: each starts at the second where the coach explains the topic, with its YouTube link at that second, the channel and two or three steps written by Morris's curation (not a transcript). Use it when the player wants to see how to fix something; for one clip by id use get_drill_clip, for the area's repeated ideas get_drill_digest, and for the player's own swing videos list_coaching_clips. Vertical videos come first; videos the player opened in full in the last six months are left out. 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": "search_drill_clips"
  }
}

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.
limitNoClips per page, 1-30. Default 10.
cursorNonext_cursor from the previous page, to get the next clips. Leave it out for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / cursor / description
      Added value: +"next_cursor from the previous page, to get the next clips. Leave it out for the first page."
    • 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."
    • addedInput schema / properties / limit / description
      Added value: +"Clips per page, 1-30. Default 10."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds non-obvious behavior: result ordering (vertical videos first) and a hidden exclusion filter (videos the player watched in full within six months are omitted). It also clarifies the steps are curated by Morris and not a transcript, which prevents misreading the output. "Read-only" is the only redundant clause.

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?

Well front-loaded: purpose and return shape come first, then routing to siblings, then the ordering/filter caveats. The middle routing sentence is dense with three semicolon-free clauses, and the trailing "Read-only." merely repeats the annotation, so it is slightly longer than necessary.

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?

There is no output schema, so the description carries the full burden of explaining what comes back, and it does: per-clip fields, ordering, and the invisible exclusion rule that would otherwise make results look incomplete. Pagination and language are handled by the schema, so nothing an agent needs to call this correctly is missing.

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 description coverage is 100%, and the schema already documents area, lang, limit and cursor with enums and defaults. The description adds only the framing that all clips belong to a single improvement area; it contributes no syntax, format or cross-parameter detail beyond the schema, so the baseline 3 applies.

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?

Specific verb + resource + scope ("List clips of one improvement area"), and it goes further by describing exactly what each clip contains: start second, YouTube link at that second, channel, and two or three curated steps. An agent can immediately distinguish this from get_drill_clip, get_drill_digest and list_coaching_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?

Gives an explicit use condition ("when the player wants to see how to fix something") and then routes to three named alternatives with the exact condition that selects each: get_drill_clip for one clip by id, get_drill_digest for repeated ideas, list_coaching_clips for the player's own videos. Nothing about tool selection is left to inference.

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