Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Recommend golf pro

recommend_golf_pro

Get the player's personal link to one pro's page on Morris, where they can buy a swing review, and record that Morris recommended that pro. Call it only for the one pro you are recommending, after find_golf_pros; never to browse pros. The recommendation is saved at once, without approval, and counts for the pro; no money is taken here: the player pays on the page.

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": {
      "slug": "<slug>"
    },
    "name": "recommend_golf_pro"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe pro's slug from find_golf_pros: lowercase letters, digits and hyphens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"The pro's slug from find_golf_pros: lowercase letters, digits and hyphens."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, non-destructive, non-idempotent), the description discloses that the recommendation is persisted immediately with no approval step, that the write is attributed 'for the pro', and that no money changes hands here because payment happens on the Morris page. That is meaningful side-effect and scope context an agent could not infer. It stops short of saying what a repeat call does, which matters given idempotentHint=false.

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 outcome (link plus recorded recommendation), then the call constraint, then the payment clarification – a sensible order with no filler. It reads as one long compound sentence, so a comma-splice density slightly hurts scanability.

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 one-parameter, non-destructive write with no output schema, it covers purpose, prerequisites, persistence behavior, and the money boundary. The only real gap is what a second call for the same pro does, which is relevant because the tool is declared non-idempotent and the description says the recommendation is 'saved at once'.

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 slug format and pattern are already documented; baseline would be 3. The description adds real semantic constraint by tying the slug to find_golf_pros as its source and emphasizing that it must be the single pro being recommended, which prevents batch or exploratory calls.

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 names two concrete effects – returning the player's personal Morris link to one pro's page and recording that the pro was recommended – and identifies the resource (a single pro, keyed by slug). An agent can distinguish it from find_golf_pros (discovery) and get_my_pro_orders (existing purchases) 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?

Explicit sequencing and exclusions: 'Call it only for the one pro you are recommending, after find_golf_pros; never to browse pros.' It states both the triggering condition and the anti-pattern, and names the sibling that must run first.

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