Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Find golf pros

find_golf_pros
Read-onlyIdempotent

List the golf pros on Morris, with their title checked by hand, who review a swing by video within 48 hours: name, title, club, city, and what they sell at what price. Use it when the player asks for a pro to look at their swing; a player who already has a pro goes to theirs. Then recommend_golf_pro gives the link to the one you recommend; for reviews already bought use get_my_pro_orders. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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' safety profile, the description discloses manual title verification, the 48-hour video-review scope, and the information returned about each pro and their prices. The final 'Read-only' statement merely confirms readOnlyHint, and operational details such as result ordering or freshness are not provided, but those are minor for this simple listing tool.

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 description is front-loaded with purpose and scope, then efficiently covers outputs, triggers, exclusions, and related tools in three sentences. It is slightly dense, and the trailing 'Read-only' repeats structured annotation information, but there is little substantive waste.

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 zero-parameter read tool without an output schema, it supplies the selection scope, service characteristics, result fields, and downstream and alternative tools needed for correct use. The main remaining ambiguity is 'a player who already has a pro goes to theirs,' which does not identify a concrete sibling tool for that path.

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?

There are no parameters, so the baseline is 4 and there is no argument syntax or meaning to clarify. The description usefully makes clear that this is a fixed-scope listing rather than a search requiring filters.

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 gives a specific verb and resource—listing golf pros on Morris—and narrows the result set to manually title-checked pros offering video swing reviews within 48 hours. It also specifies the returned fields and distinguishes the tool from recommend_golf_pro and get_my_pro_orders.

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 explicitly says to use the tool when a player asks for a pro to examine their swing and excludes players who already have a pro. It further explains the workflow: use recommend_golf_pro for the recommendation link and get_my_pro_orders for reviews already purchased.

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