Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Explain game format

explain_game_format
Read-onlyIdempotent

Cómo se juega un formato de partida de Badgie Golf (stableford, stroke = Medal, match, fourball_match, skins, sindicato, against_par, against_bogey, max_score, nassau, vegas, wolf, press = presses automáticos): pasos, un ejemplo con números, el hándicap y qué se ve en el tablero. Es el mismo texto que la hoja «¿Cómo se juega?» de la app. Úsala SIEMPRE antes de explicar cómo cuenta la app un formato de partida. Las modalidades de competición (foursome, greensome, Chapman, fourball, scramble…) y sus dudas de reglas van con explain_competition_format; todas se pueden jugar como partida de grupo con create_party.

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": {
      "format": "<format>"
    },
    "name": "explain_game_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYesThe format: stableford, stroke (medal), match, fourball_match, skins, sindicato, max_score, against_par, against_bogey, nassau, vegas, wolf or press (automatic presses).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / format / description
      Added value: +"The format: stableford, stroke (medal), match, fourball_match, skins, sindicato, max_score, against_par, against_bogey, nassau, vegas, wolf or press (automatic presses)."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent, closed-world lookup, so safety is covered. The description adds genuine behavioral context the annotations cannot: the output is verbatim the same text as the in-app "¿Cómo se juega?" sheet, and it spells out what that text contains. It stops short of noting length or language of the returned text, which keeps it from a 5.

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?

One dense, front-loaded sentence that leads with the purpose and the format list, then adds the mandatory-use rule and the sibling routing. The parenthetical re-listing of all thirteen formats duplicates the enum and is the only slack, though it does help match natural-language format names.

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?

Single-parameter lookup with no output schema, so the description must convey what comes back — and it does: steps, a worked numeric example, handicap handling, and the on-card view. Nothing an agent needs in order to call this correctly or describe the 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% and the enum already lists every value, so the baseline would be 3. The description earns one more by mapping aliases an agent would otherwise mis-resolve — "stroke = Medal" and "press = presses automáticos" — which is meaning beyond the schema's raw enum.

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 verb+resource ("Cómo se juega un formato de partida de Badgie Golf") and enumerates the exact formats covered, plus what the answer contains (pasos, ejemplo con números, hándicap, tablero). It names the sibling it is not — explain_competition_format — so an agent can separate 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 an explicit directive ("Úsala SIEMPRE antes de explicar cómo cuenta la app un formato de partida") and draws the exclusion boundary: competition modalities and their rules questions go to explain_competition_format. It even notes that all of them can be played as a group round via create_party, which resolves the most likely routing ambiguity.

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