Morris Golf

List competitions

list_competitions

Read-onlyIdempotent

Torneos amateur en España para el jugador (clubes con y sin campo, federaciones, circuitos y los que se juegan en Badgie), por sitio (campo, ciudad, isla, provincia o comunidad autónoma; sin sitio, su campo), fechas (60 días por defecto), formato y nivel; los nacionales sin sede (Campeonato de España, Final Nacional…) salen pidiéndolos por nombre (text) o por nivel. Cada prueba trae cómo apuntarse, lo que paga (entry.prices vacío: precio no publicado, nunca «gratis»), su categoría, si le cuenta para el hándicap y por qué, y la fuente con su hora de lectura. page_url es su ficha en badgie.golf/torneos (la de Badgie si se juega en Badgie): es el enlace que se le da; source y live_check_url son la fuente (federación o plataforma) y channels, cómo apuntarse. Sin venue.province, la fuente solo da la comunidad (venue.region). query.total dice cuántas hay y query.area_page_url es la página con todas las de su zona. Si nada le encaja, trae to_check (los calendarios de organizadores cercanos, que se leen con read_tournament_page) y nearest_beyond. Cita solo lo que devuelva o lo que leas en este turno en la página del organizador.

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": "list_competitions"
  }
}

Input Schema

Name	Required	Description
`for`	No	Who the competition is for: the player (me) or someone else they describe (other).
`ref`	No	ref de una prueba que ya devolvió esta herramienta, o su ficha de badgie.golf (su page_url o el enlace que pegue el jugador): trae su ficha entera.
`text`	No	Palabras del nombre de la prueba, del organizador o del campo. También encuentra las pruebas nacionales sin sede (Campeonato de España, Final Nacional…).
`when`	No	Date range; leave it out for the next 60 days.
`level`	No	Por defecto club, federación y circuito; las de élite salen solas con hándicap 4,4 o menos, o pidiéndolas. Pedir un nivel trae también las pruebas nacionales sin sede de ese nivel.
`limit`	No	Cuántas pruebas; 5 por defecto.
`where`	No	Dónde buscar. Sin where se busca alrededor de su campo habitual o, si no tiene, del campo de su licencia.
`format`	No	counts_for_handicap cuando quiere que le cuente para el hándicap.
`entries_open_only`	No	Solo pruebas con la inscripción abierta ahora.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

addedInput schema / properties / for / description

Added value: +"Who the competition is for: the player (me) or someone else they describe (other)."

addedInput schema / properties / when / description

Added value: +"Date range; leave it out for the next 60 days."

First observedNov 6, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description still adds substantial context: empty entry.prices means price unpublished, never 'free'; venue.province may be absent so only venue.region is given; query.total and query.area_page_url are provided; and it carries an explicit 'cite only what this returns or what you read this turn' rule. It also discloses the fallback path (to_check, nearest_beyond) that an agent would otherwise not anticipate.

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?

Front-loaded with the core scope and every clause carries information, but it reads as one dense run-on paragraph that blends input guidance, return-shape explanation and citation rules without any structural separation. Given nine parameters and no output schema the length is defensible; the formatting is what costs it.

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?

With no output schema, the description fully carries the return contract: what each result includes (how to enter, prices and their null semantics, category, handicap relevance and rationale, source with read time), which field is the shareable link, the query totals, and the empty-result fallbacks. An agent can call this tool and interpret the response without further information.

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 on top: level's default set and the rule that élite events appear automatically at handicap 4.4 or lower (or on request), that requesting a level also surfaces venue-less national events, and that text is the path to nationals with no venue. These behavioral couplings are not derivable from the schema alone.

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?

States a specific verb and resource with unusually precise scope: amateur tournaments in Spain (clubs with/without a course, federations, circuits, Badgie-hosted), searchable by site, dates, format and level. The scope is unmistakable, but it never names the obvious sibling get_my_competitions, so an agent must infer the split between 'competitions to enter' and 'competitions I'm entered in'.

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 concrete routing rules: nationals without a venue are found by name via text or by level; with no where it defaults to the player's home course; page_url vs source/live_check_url is spelled out; and if nothing fits it returns to_check, explicitly to be read with read_tournament_page, plus nearest_beyond. What's missing is an explicit negative case naming which sibling to use instead for the player's own entries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Morris Golf tools Inspect

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.