Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Search instruction

search_instruction
Read-onlyIdempotent

Search Badgie's instruction corpus: about 480 teaching videos distilled into eleven chapters (technique, diagnosis by ball-flight fault, drills with repetitions, practice plans). Use it before prescribing technique, a drill or a practice plan, and when commenting a swing analysis. Entries come in Spanish and without authorship: retell them in your own words and never name an instructor, school or channel. For summaries of coaches' lessons with sources use search_teacher_corpus; for scored drills get_drills. Read-only.

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": {
      "query": "<query>"
    },
    "name": "search_instruction"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many entries to return. Default 4.
queryYesWhat to look for, in golf words: «slice with the driver», «greenside bunker», «fat iron shots», «one hour a week practice plan». The corpus is Spanish, so Spanish words match best.
chapterNoOne chapter by club or situation: driver, hierros, wedges-chipping, putt, bunker; fundamentos-swing when the fault crosses clubs; mental; course-management; planes-entrenamiento for a plan; fitness-equipo; otros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / chapter / description
      Previous value: -"Capítulo por palo o situación: driver, hierros, wedges-chipping, putt, bunker; fundamentos-swing si el fallo cruza palos; mental si es de cabeza; course-management para estrategia; planes-entrenamiento para un plan; fitness-equipo; otros."New value: +"One chapter by club or situation: driver, hierros, wedges-chipping, putt, bunker; fundamentos-swing when the fault crosses clubs; mental; course-management; planes-entrenamiento for a plan; fitness-equipo; otros."
    • changedInput schema / properties / limit / description
      Previous value: -"Entradas a traer (defecto 4)."New value: +"How many entries to return. Default 4."
    • changedInput schema / properties / query / description
      Previous value: -"Qué busca, en español y con palabras de golf: 'slice con el driver', 'salir del búnker de green', 'golpe pesado con hierros', 'plan de práctica 1 hora a la semana'."New value: +"What to look for, in golf words: «slice with the driver», «greenside bunker», «fat iron shots», «one hour a week practice plan». The corpus is Spanish, so Spanish words match best."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint false), so the bar is low, but the description adds substantive behavioral constraints: entries are Spanish-only, carry no authorship, must be retold in the agent's own words, and instructors/schools/channels must never be named. Those are operational rules an agent could not derive from any structured field.

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?

Four sentences, front-loaded with the resource and scope before routing and content-usage rules. The trailing 'Read-only' largely restates the annotations and is the one line that does not earn its place.

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?

With no output schema, the description still tells the agent what entries look like (Spanish, unattributed) and how to handle them, which is the main risk for this tool. What is missing is minor: return shape and ranking behavior are unstated, though limit and chapter are fully covered by the schema.

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 the schema already documents query examples, the chapter enum values, and the limit default of 4. The description's mention of eleven chapters and the Spanish corpus reinforces the query-language hint but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb and resource ('Search Badgie's instruction corpus') and quantifies scope ('about 480 teaching videos distilled into eleven chapters') with the chapter taxonomy in parentheses. It explicitly separates itself from two siblings by name, so an agent can pick it without opening any 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?

It gives an explicit when-to-use trigger ('before prescribing technique, a drill or a practice plan, and when commenting a swing analysis') plus two named alternatives with the condition that selects each ('search_teacher_corpus' for sourced coach lessons, 'get_drills' for scored drills). Nothing is left to inference.

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