Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Stableford

stableford
Read-onlyIdempotent

Calculate the Stableford points of a round from each hole's par, stroke index and gross score with a playing handicap: total, front nine and back nine. Use it instead of adding points by hand; get the playing handicap from playing_handicap. Pure calculation; reads and saves nothing.

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": {
      "par": "<par>",
      "si": "<si>",
      "gross": "<gross>",
      "playing_handicap": "<playing_handicap>"
    },
    "name": "stableford"
  }
}

Input Schema

NameRequiredDescriptionDefault
siYesStroke index of each hole, in hole order.
parYesPar of each hole, in hole order.
grossYesGross strokes on each hole, in hole order; null for a hole not finished.
playing_handicapYesThe player's playing handicap for the round, as from playing_handicap.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / gross / description
      Added value: +"Gross strokes on each hole, in hole order; null for a hole not finished."
    • addedInput schema / properties / par / description
      Added value: +"Par of each hole, in hole order."
    • addedInput schema / properties / playing_handicap / description
      Added value: +"The player's playing handicap for the round, as from playing_handicap."
    • addedInput schema / properties / si / description
      Added value: +"Stroke index of each hole, in hole order."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The statement "Pure calculation; reads and saves nothing" corroborates readOnlyHint/idempotentHint and adds a useful compute-only framing that annotations alone imply but don't phrase. It also discloses the three-part result shape (total, front nine, back nine), valuable since there is no output schema. It does not explain how null (unfinished) holes affect point allocation, which is the main behavioral gap remaining.

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?

Three tight sentences, front-loaded with what it computes and the inputs, followed by usage guidance and the purity note. No filler or repetition.

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 4-parameter, fully documented, fully required pure-computation tool with no output schema, the description covers purpose, inputs, dependency, and result structure. The only shortfall is silence on edge-case semantics for unfinished holes and on handicap stroke allocation, which an agent may need to set expectations.

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% and each parameter is already documented (hole order, ranges, null for unfinished holes, playing handicap source), so the schema does the heavy lifting. The description restates the same inputs and the playing_handicap origin rather than adding interpretation rules (e.g., how strokes are allocated by stroke index). Baseline 3 is appropriate.

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 and resource ("Calculate the Stableford points of a round") plus the exact inputs (par, stroke index, gross, playing handicap) and the exact outputs (total, front nine, back nine). An agent can distinguish this from scoring/reporting siblings like get_scorecard_stats or get_round_card 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 Guidelines5/5

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

Gives an explicit alternative to avoid ("instead of adding points by hand") and names the prerequisite tool for a required parameter ("get the playing handicap from playing_handicap"). The condition that selects this tool 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