Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get drill clip

get_drill_clip
Read-onlyIdempotent

Read one clip of the drill library by its id: YouTube link at the right second, channel and curated steps. Use it to reopen a clip already found with search_drill_clips or get_drill_digest; to browse an area use search_drill_clips. Answers clip_not_found when the player opened that video in full in the last six months. 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": {
      "clip_id": "<clip_id>"
    },
    "name": "get_drill_clip"
  }
}

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.
clip_idYesThe clip's id (UUID), from search_drill_clips or get_drill_digest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / clip_id / description
      Added value: +"The clip's id (UUID), from search_drill_clips or get_drill_digest."
    • 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.5/5.0
Behavior4/5

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

Annotations already establish that the operation is read-only, idempotent, and non-destructive, so the description does not need to repeat that. It adds useful non-obvious behavior by explaining that a clip can return clip_not_found when the player opened that video in full within the last six months.

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?

The description is front-loaded with the core action and return content, then follows with usage routing and the edge-case error. Three sentences carry the necessary context without filler.

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?

For a simple read-only lookup with two fully documented parameters and no output schema, the description supplies purpose, when to use it, the relevant alternative, and a notable error condition. Nothing material is missing for an agent to select and 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?

Schema description coverage is 100%, so the input schema already explains both clip_id (UUID from search_drill_clips or get_drill_digest) and lang. The description reinforces that lookup is by id but does not add meaning beyond the schema for either parameter.

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: read one clip of the drill library by its id. It also lists the key returned content (YouTube link at the right second, channel, curated steps) and distinguishes this from browsing via search_drill_clips.

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?

It explicitly says to use this to reopen a clip already found with search_drill_clips or get_drill_digest, and directs browsing to search_drill_clips instead. That gives the agent both the intended use and the alternative tool for a different task.

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