Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get swing analyses

get_swing_analyses
Read-onlyIdempotent

List the player's recent swing analyses (app and WhatsApp): date, priority, drill and progress, each with its id. Use it to compare several or follow their evolution; to discuss one in full call get_swing_analysis with its id, and for videos with ball trace or a pro's review use list_coaching_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": "get_swing_analyses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many analyses to return. Default 3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Cuántos traer (defecto 3)."New value: +"How many analyses to return. Default 3."
  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=true, so the trailing 'Read-only' adds no information. The description does add real behavior beyond the annotations: the scope is 'recent' analyses across two source channels, and it tells the agent which fields come back, which matters for a tool with no output schema. No pagination or cursor behavior is described, but limit is capped in-schema.

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?

Front-loaded with the core purpose, then routing alternatives, with no filler sentences — dense but readable. The closing 'Read-only' is redundant against readOnlyHint=true and is the one phrase that does not earn its place.

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?

For a simple one-parameter list tool with no output schema, the description covers what is returned, where the data comes from, and how it differs from alternatives. The main omission is noting that results are capped at a small number (max 5), which would matter to an agent expecting a long history, but that is documented in the schema.

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 there is a single optional 'limit' parameter fully documented in the schema, so the baseline is 3. The description only implies bounded recency via 'recent' and does not mention the hard maximum of 5, adding nothing beyond the schema.

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?

States a specific verb+resource ('List the player's recent swing analyses'), names the sources (app and WhatsApp), and enumerates the returned fields (date, priority, drill, progress, id). It also explicitly distinguishes itself from the two nearest siblings, get_swing_analysis and list_coaching_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?

Gives explicit when-to-use guidance ('to compare several or follow their evolution') plus concrete alternatives for the adjacent cases: get_swing_analysis when discussing a single analysis in full, list_coaching_clips for ball-trace videos or pro reviews. The agent needs no inference to route correctly.

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