Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Search wagr player

search_wagr_player
Read-onlyIdempotent

Busca al jugador en el WAGR (ranking mundial amateur de la R&A y la USGA, público) por nombre completo, con su país si lo sabes. Úsala cuando diga que compite en WAGR o sea júnior o amateur de alto nivel, y NO enlaza nada. match = unique: una coincidencia clara, enséñale la ficha (nombre, país y puesto) y pregúntale si es él; several: enséñale las opciones y deja que elija; none: dile que no sale y no insistas (WAGR solo lista a quien tiene ranking esta semana). needs = full_name: pídele nombre y apellido. Para enlazar, link_wagr_player con el wagr_profile de la ficha que confirme.

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

Input Schema

NameRequiredDescriptionDefault
nameYesSu nombre completo («Mateo Hidalgo»); con dos apellidos si los tiene.
countryNoSu país, código ISO («ES») o nombre en inglés; si falta se usa el de su ficha.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavior beyond them: the three outcome states (unique/several/none), what the agent should do in each, and the domain constraint that WAGR only lists players who hold a ranking that week — which explains empty results. With no output schema, this result-state disclosure is exactly the missing context.

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?

Dense and front-loaded: purpose first, then the trigger, then the result-handling branches, then the handoff. The semicolon-chained branches make it slightly hard to scan, but every clause carries an instruction the agent needs.

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 two-parameter lookup with no output schema, the definition covers the search input, the trigger conditions, all three result branches with agent actions, and the follow-up tool. Nothing needed to call or act on the result is absent.

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%, so both parameters are already documented, including the ISO-code-or-English country input and its fallback. The description restates full name and country and adds a small operational cue (ask for first and last name), but nothing about matching tolerance or normalization beyond the schema.

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?

States a specific verb and resource: look up a player in the WAGR amateur world ranking by full name, optionally with country. It also explicitly delimits scope against the sibling it pairs with by saying it does not link anything ("NO enlaza nada"), leaving link_wagr_player as the distinct write path.

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?

Gives an explicit trigger (the user says they compete in WAGR, or is a junior/high-level amateur) and an explicit next step for the linking case (link_wagr_player with the wagr_profile from the confirmed card). The boundary against the linking tool is stated rather than inferred.

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