Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get round shots

get_round_shots
Read-onlyIdempotent

Los golpes de una vuelta suya con GPS (de su Garmin o marcados en la app), hoyo a hoyo: el palo, los metros y de dónde sale y dónde cae cada golpe (tee, calle, rough, búnker, green). Úsala cuando pregunte qué palo sacó en un hoyo, hasta dónde llegó o por dónde se le fue. shots vacío: esa vuelta no tiene golpes medidos, como una tarjeta apuntada o una oficial. Garmin no siempre registra los putts. Para la tarjeta sin golpes está get_round_card.

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": {
      "round_id": "<round_id>"
    },
    "name": "get_round_shots"
  }
}

Input Schema

NameRequiredDescriptionDefault
holeNoSolo los golpes de este hoyo.
round_idYesUna vuelta suya (id de list_rounds o get_round_history, origen distinto de rfeg y trackman).
with_mapNoAñade las coordenadas de cada golpe y la foto aérea de cada hoyo, para pintarlos. Sin ella no hacen falta.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: empty shots means the round was scorecard-only or official, and Garmin does not always record putts. It stops short of describing ordering, units or volume of returned shots.

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-loads what the tool returns, then the usage trigger, then the empty-state caveat and the alternative — a sensible order with no filler sentences. Slightly dense colon-chained phrasing, but every clause carries information.

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 3-parameter read tool with full schema coverage, no output schema and safe annotations, the description covers source limitations, empty results, putt-recording caveats and the fallback tool. Only the relationship to the similarly named get_shots is left unexplained.

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 coverage is 100%, so the schema already documents hole, round_id and with_map, including the note that with_map adds coordinates and aerial imagery. The description adds only the provenance constraint (GPS-measured shots) rather than any new per-parameter meaning, 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?

States a specific verb+resource: the GPS-measured shots of one of the user's rounds, hole by hole, including club, distance and lie from/to. It enumerates the data fields (tee, calle, rough, búnker, green) and scopes the source (Garmin or app-tracked), which lets an agent distinguish it from a scorecard tool without opening the schema.

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?

Gives an explicit trigger ('cuando pregunte qué palo sacó en un hoyo, hasta dónde llegó o por dónde se le fue') and routes the no-shots case to get_round_card. The gap is the sibling get_shots, which is never mentioned or differentiated, so an agent facing both names has to guess.

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