Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get green reads

get_green_reads
Read-onlyIdempotent

Su libreta de caídas de green: las pendientes que él midió con el móvil en la app (Medir la caída), por campo y hoyo, con la fecha. Con campo y hoyo añade, si el campo lo tiene, la caída del green entero medida desde el aire. Úsala cuando prepare un campo o un hoyo, cuando pregunte cómo cae un green o qué midió en un hoyo. Sin course_id da las últimas de todos sus campos.

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

Input Schema

NameRequiredDescriptionDefault
holeNoUn hoyo de ese campo.
course_idNoEl campo (course_id de get_course_profile o get_round_history).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description focuses on behaviour the annotations cannot express: with course and hole it also returns the whole-green aerial slope, but only if that course has it, and with no course_id it returns the most recent readings across all the user's courses. Missing only return formatting/units detail.

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?

Three sentences, front-loaded with what the data is, then the conditional enrichment, then usage triggers and the no-course default. No filler; the only slight cost is the dense parenthetical naming of the in-app feature, which is nonetheless informative.

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 two-optional-parameter read tool with annotations and no output schema, the description covers what is returned, how the result varies with the parameters, and when to call it. Minor gaps remain around slope units/format and result ordering beyond 'most recent', which an agent could not fully infer.

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 real meaning beyond the schema: it explains the conditional enrichment when both course and hole are supplied, and the default behaviour when course_id is omitted. It also implies hole is meaningful in the context of a course, which the schema alone does not make explicit.

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 precisely what the tool returns: the user's own green-slope readings measured with the phone app ('Medir la caída'), organized by course and hole with dates, plus optionally an aerial whole-green slope. That is specific enough to separate it from neighbouring tools like get_hole_plan, get_course_intel or get_shots without opening any 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 explicit usage triggers: when the user is preparing a course or hole, asks how a green breaks, or asks what they measured on a hole. It does not name a competing tool or state exclusions, so it stops short of a 5, but the when-to-use context is unambiguous.

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