Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get tournament calendar

get_tournament_calendar
Read-onlyIdempotent

The tournaments the player can enter over the next weeks or months, by their handicap and category, around their course or a place (or all of Spain), with date, course, format, whether it counts for handicap, the source and whether they already entered. Use it for «which tournaments can I play until January», «WAGR events in Spain» or «what counts to lower my handicap in Madrid»; for one event in full use list_competitions. Follow its «say». 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_tournament_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD. Default 90 days after from; one year at most.
fromNoFirst day, YYYY-MM-DD. Default today.
wagrNotrue for events that count for the World Amateur Golf Ranking.
placeNoProvince, region, city or course as the player says it. Leave it out to search around their course.
spainNotrue when they want all of Spain (180 days at most).
counts_for_handicapNotrue for events that count to lower their handicap.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the trailing "Read-only" adds nothing. What does add value is the enumeration of returned fields (date, course, format, handicap relevance, source, already-entered flag), which matters because there is no output schema. The phrase "Follow its «say»" is opaque jargon that conveys no actionable behavior.

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

Conciseness3/5

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

Purpose is front-loaded correctly, but the opening sentence is a long stacked clause list that is hard to parse, and "Follow its «say»" is a fragment that consumes space without meaning. The examples and sibling routing earn their place; the cryptic fragment does not.

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 six-parameter, zero-required read tool with no output schema, the description covers what is returned, the location-scope choice between place and spain, and the handoff to list_competitions. It stops short of explaining result ordering or volume, which would matter for an open-ended calendar query, but nothing essential to invoking it correctly is missing.

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 description coverage is 100%, so all six parameters are already documented, including the from/to defaults and the one-year and 180-day caps. The description adds only framing — that filtering happens by the player's handicap and category, and that omitting place searches around their course — without new syntax or precedence rules. Baseline 3 is appropriate when the schema carries the semantics.

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?

Opens with a specific resource (tournaments) and enumerates the retrieval dimensions — handicap, category, location scope, date range — plus the fields returned. It explicitly separates itself from the sibling list_competitions ("for one event in full use list_competitions"), so an agent can route between the two without opening either 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 three concrete natural-language query examples ("which tournaments can I play until January", "WAGR events in Spain", "what counts to lower my handicap in Madrid") that map directly onto the wagr, spain and counts_for_handicap parameters, and names the alternative tool for the single-event case. When-to-use and when-to-use-something-else are both explicit.

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