Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get local rules

get_local_rules
Read-onlyIdempotent

Local rules checked against the official document, with source and date: the permanent 2026 local rules of the Spanish federation (RFEG) and of the Andalusian (RFGA) and Madrid (RFGM) federations, and a course's own when Morris has them. Use it for «I play X today, which local rules apply?» or to compare federations. A course with no rows means Morris does not have its local rule: say so, give the general rule and suggest asking the starter. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
topicNoThe situation: «stones in bunkers», «preferred lies», «out of bounds».
courseNoThe course as the player names it.
federationNoFederation acronym or region: RFEG, RFGA, RFGM, Andalucía, Madrid.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, and the trailing "Read-only" merely restates that. The description does add useful behavior beyond annotations: rules are checked against the official document, carry source and date, and empty results have a defined handling path. It does not describe the response shape (e.g., how source/date are presented), so this is solid but not rich.

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?

The core purpose is front-loaded in the first clause, and the usage example and fallback follow logically. The opening sentence is long and stacked with parenthetical federation acronyms, which slightly taxes scanning, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with three optional parameters and no output schema, the description covers purpose, eligible sources, comparison use case, and empty-result behavior. Nothing an agent needs to call it or to interpret a zero-row result is missing.

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 per-dimension baseline is 3, but the description adds real meaning: it enumerates the specific federations recognized (RFEG, RFGA, RFGM, Andalucía, Madrid) and clarifies that the course parameter matters only when Morris has that course's own rule. That clarifies how the three optional filters interact.

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?

The description names a specific resource (local rules) and scopes it precisely: permanent 2026 RFEG/RFGA/RFGM rules plus a course's own rule when available, each with source and date. It clearly differs from sibling rule tools like get_rule or search_rules by being federation/course-specific and dated, though it never names those siblings to sharpen the contrast.

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?

It gives two explicit triggering scenarios ("I play X today, which local rules apply?" and comparing federations) and even prescribes the fallback when a course has no rows: say so, give the general rule, and suggest asking the starter. That is genuine when-to-use plus when-not-to-expect-results guidance.

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