Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get coaching clip

get_coaching_clip
Read-onlyIdempotent

Read one coaching clip in full by its id from list_coaching_clips: for a swing, the whole analysis, the video with the ball trace and the pro it was sent to; for a pro review, the player's question and what the pro sent back; for a coach's video analysis, what the coach wrote. For a clip of the drill library use get_drill_clip. 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": {
      "id": "<id>"
    },
    "name": "get_coaching_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe clip id from list_coaching_clips: swing:<uuid>, pro:<uuid> or coach:<uuid>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"El id del clip, como swing:<uuid>, pro:<uuid> o coach:<uuid>."New value: +"The clip id from list_coaching_clips: swing:<uuid>, pro:<uuid> or coach:<uuid>."
  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 non-destructive, so safety is covered. The description adds genuinely new context beyond that: what payload comes back for each of the three clip types (analysis plus ball-trace video and recipient pro; player question plus pro reply; coach write-up). It does not mention failure behavior for an unknown or malformed id, which keeps it from a 5.

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?

Purpose and id source are front-loaded, and the sibling redirect is placed clearly before the trailing 'Read-only' note. The middle clause enumerating return contents for three clip types is long but each item is informative rather than filler.

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 one parameter and no output schema, the description carries the return-value burden and does so by describing what each clip type yields. It is nearly complete for this complexity; only error/not-found behavior is unaddressed.

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 the id format with the swing:/pro:/coach: prefixes. The description adds only the pointer to list_coaching_clips as the id source, so baseline 3 is appropriate.

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 opens with a specific verb and resource ('Read one coaching clip in full by its id') and immediately states its provenance ('from list_coaching_clips'). It distinguishes itself from the closest sibling by naming get_drill_clip as the tool for drill-library 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 where the id comes from (list_coaching_clips) and states the exclusion condition: use get_drill_clip for drill-library clips. An agent can pick between the two without opening either schema.

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