Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get swing analysis

get_swing_analysis
Read-onlyIdempotent

Read one of the player's swing analyses, made in the app or by Morris on WhatsApp: the priority with the feel to look for, the drill with its repetitions, progress against the previous analysis, what is seen at each moment and the measurements behind the diagnosis. Call it before talking about their technique. Without id, their latest own swing; an id from get_swing_analyses may also be a video of someone else they sent, marked de_otra_persona. To compare several use get_swing_analyses; for the video with its ball trace use get_coaching_clip. 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": "get_swing_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe analysis id, from get_swing_analyses. Default: the latest analysis of their own swing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"El análisis concreto; por defecto, el último."New value: +"The analysis id, from get_swing_analyses. Default: the latest analysis of their own swing."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent and the description still adds non-obvious behavior: the default target is the player's latest own swing, and an id can point at a video of someone else marked de_otra_persona, which materially changes how the result should be interpreted. It also previews the return content, which no structured field provides.

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?

It is a single dense paragraph that is front-loaded with purpose and ends with routing and a read-only note. Every sentence carries information, though the closing "Read-only." duplicates annotations and the payload enumeration is a long clause chain.

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?

With no output schema, the description must convey what comes back, and it does so explicitly (priority/feel, drill/reps, progress, per-moment observations, measurements). Combined with the default-id rule, the sibling routing and the cross-person caveat, nothing needed 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the id may reference a third-party video flagged de_otra_persona, and omission yields the latest analysis of their own swing. That extra provenance nuance justifies going above baseline.

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 of the player's swing analyses") and enumerates the payload an agent will get back: priority with the feel, drill with repetitions, progress versus the previous analysis, per-moment observations and measurements. It clearly distinguishes this from get_swing_analyses and get_coaching_clip by name.

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 states a positive trigger ("Call it before talking about their technique") and routes to alternatives for adjacent needs: get_swing_analyses to compare several, get_coaching_clip for the video with ball trace. The default when id is omitted is also spelled out.

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