Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Connect link

connect_link
Read-onlyIdempotent

Get the address of the player's Morris connections page, where they connect RFEG, Garmin or TrackMan themselves. Use it when get_connections or connections_line shows a source missing or failing. The page needs the player signed in to morris.golf in their browser. Read-only: it connects nothing and never returns a token.

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": {
      "connector": "<connector>"
    },
    "name": "connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectorYesThe source the player wants to connect: rfeg (Spanish federation), garmin (watch) or trackman (launch monitor). The same page serves all three.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / connector / description
      Added value: +"The source the player wants to connect: rfeg (Spanish federation), garmin (watch) or trackman (launch monitor). The same page serves all three."
  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 readOnly/idempotent annotations, it discloses an external prerequisite (the player must be signed in to morris.golf in their browser) and sets expectations that it 'connects nothing and never returns a token' — a key negative guarantee that prevents misuse as an action tool. No return-format detail is given, but the annotations already carry the safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what the tool returns, then when to use it, then the prerequisite and safety note. No redundant or filler wording.

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?

For a single-parameter, no-output-schema tool with full annotation coverage, the description supplies everything an agent needs: what is returned (an address, not a token), when to call it, and the sign-in prerequisite. Nothing material is missing.

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 enum already explains rfeg/garmin/trackman plus the fact that one page serves all three. The description's prose mentions the same three sources but adds no format or behavioral detail about the connector argument beyond the schema, so 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?

Specific verb plus resource: 'Get the address of the player's Morris connections page'. The description also distinguishes the tool from its closest siblings (get_connections, connections_line) by explaining that this page is where the player connects sources 'themselves'.

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 trigger condition: 'Use it when get_connections or connections_line shows a source missing or failing'. It names the alternatives and the state that should route the agent here, leaving nothing 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