Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

List coaching clips

list_coaching_clips
Read-onlyIdempotent

List the player's coaching clips, newest first: their swing videos with Morris's analysis and ball trace, what a Morris pro sent back, and their school coach's video analyses. Use it when they ask about their videos or what their pro said, or before send_swing_to_pro; open one with get_coaching_clip. Clips from other coaches' YouTube lessons are another library: search_drill_clips. 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_coaching_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly one kind: swing (their videos), pro_review (a Morris pro's review) or coach_analysis (their coach's video analysis).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"Solo un tipo: swing, pro_review o coach_analysis."New value: +"Only one kind: swing (their videos), pro_review (a Morris pro's review) or coach_analysis (their coach's video analysis)."
  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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: results are ordered newest first and the payload mixes three distinct artifact types. The trailing 'Read-only' merely restates the annotation, which is why this is a 4 rather than 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?

Three sentences, front-loaded with the resource and its contents, then usage, then alternatives. Dense but every clause carries routing information; the only waste is the redundant 'Read-only' tag at the end.

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, and the description compensates by describing what each clip kind contains and the sort order. For a one-optional-parameter list tool with full annotation coverage, nothing an agent needs in order to call it 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 single enum parameter is fully documented in the schema, including the meaning of each of the three values. The description adds no filtering syntax or default behavior beyond what the schema states, 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?

The description opens with a specific verb and resource ('List the player's coaching clips') and immediately enumerates the three content types returned (swing videos with analysis and ball trace, pro reviews, coach video analyses). It also names the sibling libraries it is not (search_drill_clips for other coaches' YouTube lessons), so an agent can distinguish it without opening a 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?

It gives explicit triggers ('when they ask about their videos or what their pro said'), a sequencing rule ('before send_swing_to_pro'), a follow-up path ('open one with get_coaching_clip'), and a clear exclusion routing to search_drill_clips. This is the full when/when-not/alternatives pattern.

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