Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get scorecard stats

get_scorecard_stats
Read-onlyIdempotent

Calcula cualquier cifra o cruce de SUS tarjetas hoyo a hoyo: pares o mejor, birdies, greens, calles, putts (1, 2 y 3 o más; «green a tres» son tres putts), metros del primer putt y cuántos mete según la distancia, lado del fallo, up & down, sand saves, scrambling, penalizaciones y búnkeres. ÚSALA para porcentajes y preguntas de «cuando...»: «¿qué % de pares hago cuando cojo green?», «¿cuántos tres putts hago?», «¿cuántos meto de 2 a 4 metros?», «¿a qué lado fallo?», «¿cómo voy en los par 3?». Sin filtros trae el global con cortes por green, par y calle; con filtros, esos hoyos. Llámala SIEMPRE antes de decir que un dato no está o no está separado. Ventana: últimas 20 tarjetas; rounds la amplía hasta 80; con course o months cuenta todas las de ese campo o plazo, hasta 80. Si devuelve course_ambiguous, pregunta cuál.

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

Input Schema

NameRequiredDescriptionDefault
girNotrue: hoyos con green cogido; false: con green fallado.
parNoOnly holes of this par: 3, 4 or 5.
holeNoUn número de hoyo; úsalo con course.
puttsNoHoyos con esos putts; 3 = tres o más.
courseNoUn campo: el nombre que dice el jugador o su course_key.
monthsNoSolo tarjetas de estos últimos meses.
roundsNoCuántas tarjetas recientes contar; defecto 20, o hasta 80 con course o months.
sourceNolive: vueltas de Badgie; rfeg: oficiales; all: las dos.
fairwayNoSalida en calle, fallada, o fallada a la izquierda o a la derecha. Solo pares 4 y 5.
up_and_downNotrue: up & down conseguido; false: fallado.
miss_directionNoLado por el que falló el green.
proximity_max_mNoTras el golpe a green, a menos de estos metros del hoyo.
proximity_min_mNoTras el golpe a green, a estos metros o más del hoyo.
first_putt_max_mNoPrimer putt de menos de estos metros.
first_putt_min_mNoPrimer putt desde estos metros, incluidos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / par / description
      Added value: +"Only holes of this par: 3, 4 or 5."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds genuinely new behavior: default window of the last 20 scorecards, extension to 80 via rounds, counting all rounds for a given course or month window up to 80, and a specific error path (course_ambiguous → ask which course). It also explains the shape of the result set (global with breakdowns by green, par, fairway vs. filtered holes).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then use cases, then concrete example questions, then scope defaults and the ambiguity fallback. The metric enumeration is long but every item maps to a filter or a user question, so nothing is padding.

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 15-parameter, no-output-schema analytic tool, the description carries the needed load: what is computed, what population is used, how filters narrow it, and how ambiguity is surfaced. The only residual gap is that the returned field structure is only sketched ('cortes por green, par y calle') rather than described, which matters somewhat given there is no output schema.

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 description coverage is 100%, so the baseline is 3; the description still earns credit by explaining cross-parameter behavior that the schema cannot express — no filters yields a global breakdown by green/par/fairway while filters reduce the population to those holes. It also glosses 'green a tres' as three putts, resolving an ambiguous phrase. It doesn't clarify interaction rules between proximity/putt range pairs, so not a 5.

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?

Uses a concrete verb ('Calcula') plus a well-scoped resource ('cualquier cifra o cruce de SUS tarjetas hoyo a hoyo') and enumerates the exact metrics covered (pares, birdies, greens, calles, putts, up & down, sand saves, scrambling, penalizaciones). An agent immediately knows this is the hole-level aggregation tool. It stops short of naming a sibling (e.g. get_par_type_stats or get_my_strokes_gained) as the alternative, which keeps it from a 5.

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?

Explicitly states when to call it ('ÚSALA para porcentajes y preguntas de «cuando...»') and reinforces with four realistic query phrasings that map to the tool. It also adds a strong routing rule: always call it before claiming a datum is missing or not broken down, which prevents the agent from falling back to other tools.

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