Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get shots

get_shots
Read-onlyIdempotent

Sus golpes de varias vueltas filtrados por palo, lie de salida, tipo de golpe, campo, hoyo y distancia a la bandera, cada uno con sus golpes ganados, y un resumen (golpes ganados por golpe, por categoría, distancia mediana). Úsala para preguntas como «¿qué tal pego el 7 desde el rough?», «¿cómo me salen los approach de 100 a 150?» o «¿qué hago en el 7 de mi campo?». Lee golpes del reloj (Garmin) y marcados a mano; no admite consultas libres.

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_shots"
  }
}

Input Schema

NameRequiredDescriptionDefault
lieNoDesde dónde salió el golpe.
limitNoGolpes listados como máximo. 30 si no se indica; el resumen cuenta todos.
club_typeNoClub type: driver, 3-wood, 5-wood, 7-wood, hybrid, 2-iron to 9-iron, pw, gw, sw, lw (and putter where listed).
course_idNoUn campo concreto (course_id de get_course_profile o get_round_history).
shot_typeNoShot type: TEE, APPROACH, LAYUP, CHIP, RECOVERY or PUTT.
from_max_mNoOnly shots from at most this distance to the flag, in metres.
from_min_mNoDistancia mínima a la bandera antes del golpe, en metros.
hole_numberNoOnly this hole number, 1-18; best with a course.
last_roundsNoVueltas recientes que mirar. 20 si no se indica.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / club_type / description
      Added value: +"Club type: driver, 3-wood, 5-wood, 7-wood, hybrid, 2-iron to 9-iron, pw, gw, sw, lw (and putter where listed)."
    • addedInput schema / properties / from_max_m / description
      Added value: +"Only shots from at most this distance to the flag, in metres."
    • addedInput schema / properties / hole_number / description
      Added value: +"Only this hole number, 1-18; best with a course."
    • addedInput schema / properties / shot_type / description
      Added value: +"Shot type: TEE, APPROACH, LAYUP, CHIP, RECOVERY or PUTT."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description only needs to add data-provenance and shape details — and it does: shots come from the Garmin watch and from manual tagging, and the result includes strokes gained per shot plus a summary. The 'no free-form queries' constraint is genuine behavioral context not present in the 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?

Purpose is front-loaded in the first clause, followed by filter list, output shape, and usage examples in a logical order. The sample-question sentence is long but each example earns its place by mapping to a distinct filter combination.

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 nine optional parameters and no output schema, the description carries the return-value burden and does so reasonably: per-shot strokes gained plus a summary broken down per shot, per category, and by median distance. Minor gaps remain — no mention of ordering or how listed shots are sorted, and no note on what happens when no filters are supplied.

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 every parameter is already documented, including the limit default and its effect on the summary. The description restates the filter dimensions collectively but adds no syntax, interaction, or format detail beyond what the schema provides, landing at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete resource (shot-level data across multiple rounds) plus the filter dimensions (club, lie, shot type, course, hole, distance to flag) and the payload (per-shot strokes gained plus an aggregate summary). The 'varias vueltas' phrasing implicitly separates it from per-round siblings like get_round_shots, but no sibling is named, so the differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Three concrete sample questions (7-iron from the rough, approaches from 100-150, hole 7 of my course) give an agent strong positive routing signals. It also closes one door with 'no admite consultas libres', routing free-form questions elsewhere, but it never explicitly names which alternative to use for single-round or free-form cases.

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