Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Search morris library

search_morris_library
Read-onlyIdempotent

Search Morris's own golf library: golf history, players, tournaments and stories; the R&A and USGA Rules of Golf explained (definitions and referees' cases); lessons from golf podcasts and videos on strategy, short game, putting, equipment, the mental game and practice; what the coaches of the drill library teach by fault; technique and physics figures with their source. Each result carries its sources. Present what coaches teach as what those channels teach, never as golf's truth. 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_morris_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for, in a few words: «slice causes», «Seve Ballesteros 1984 Open», «Rule 16.1».
latestNotrue to bring the latest golf news the library holds first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the trailing 'Read-only' is redundant. What the description does add is genuinely behavioral: each result carries its sources, and coach-sourced material must be attributed to those channels rather than asserted as golfing truth. That framing note materially shapes how results should be reported.

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 coverage inventory and the attribution rule are front-loaded and each clause earns its place by naming a distinct indexed corpus. The trailing 'Read-only' repeats annotation data and is dead weight, and the single long semicolon chain is dense but still parseable.

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 two-parameter read-only search with no output schema, the agent knows what corpora exist, that results are source-attributed, and how to present coach-derived claims. Only result volume, ranking behaviour and overlap with the narrower search siblings remain unaddressed.

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 both parameters are already documented in the schema, including worked query examples and the 'latest' news-ordering flag. The description adds no query syntax, result-count or ranking semantics beyond that, so the baseline 3 applies.

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 verb+resource is specific ('Search Morris's own golf library') and the description enumerates the indexed domains: golf history, Rules of Golf definitions and referees' cases, podcast/video lessons, drill-library coaching by fault, and technique/physics figures. This scopes it against near-neighbours like search_rules, search_instruction and search_teacher_corpus by content breadth, though it never names an alternative outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the coverage list: reach for it when the question spans history, rules, coaching content or technical figures. There is no explicit when-not clause and no routing to sibling search tools that cover narrower corpora, so the agent must infer the boundary.

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