Skip to main content
Glama

Get my scoring

get_my_scoring
Read-onlyIdempotent

Sus números de juego como los lee un entrenador universitario de EE. UU., los mismos que imprimen su ficha Road to USA y su PDF: todas sus vueltas de los últimos 12 meses, las oficiales de la federación (RFEG) y las de torneos WAGR juntas (un torneo WAGR que está en la RFEG cuenta una vez; las del extranjero van solo con golpes, to_par null), su media y su mejor vuelta; medias por contexto (all; wagr frente a rfeg; away = fuera de su club; final = última vuelta de un torneo); las cifras oficiales RFEG (bajo par, vueltas en los 60, mejor vuelta del año y de su carrera); su vuelta típica de 18 hoyos (eagles, birdies, pares, bogeys y dobles o peor); por tipo de par; por año; y su WAGR: puesto de ESTA semana, mejor puesto, Europa (EGA, rank de total) y cada temporada con sus resultados (tier win, top10, top20, field, cut). Úsala cuando pregunte por su media, su mejor vuelta, cómo rinde fuera o en la última vuelta, sus resultados o su puesto WAGR, o qué ve un entrenador en sus números. Si wagr.rank es null y off_list incluye wagr, no está en el ranking de esta semana: dilo así, con last_ranked; nunca des un puesto antiguo como actual. Son golpes, no hándicap: para el hándicap, get_my_golf_data.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, but the description adds substantive semantics beyond them: a de-duplication rule (a WAGR event that is also RFEG counts once; foreign events carry strokes with to_par null) and a critical edge-case instruction that a null wagr.rank with wagr in off_list means unranked this week and must be reported with last_ranked, never an old rank as current. Those are exactly the output-interpretation hazards that cause wrong answers, and they are disclosed here rather than left to inference.

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

Conciseness3/5

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

A single semicolon-chained sentence carries the entire contents inventory before any guidance appears, so the agent must scan a dense block to reach the actual usage rule and the WAGR null warning. Much of the inventory is genuinely necessary because there is no output schema, but the lack of structure and front-loading of guidance costs it. Every clause is informative, yet the shape is a wall of text rather than a prioritized statement.

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?

With no output schema and no parameters, the description bears the full load of return-value explanation and does so exhaustively: data sources, merge rules, context splits, official RFEG figures, typical-round breakdown, and WAGR season detail. It also supplies the failure-mode handling for unranked players and the domain boundary against handicap data, leaving nothing an agent needs in order to call and interpret it.

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?

The schema has zero parameters, so the baseline is 4; there is nothing parameter-wise the description could add. It correctly contains no input guidance, keeping the space for output semantics instead.

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 opening clause frames the resource precisely ('sus números de juego como los lee un entrenador universitario de EE. UU.'), then enumerates the concrete contents: rounds from the last 12 months, RFEG official rounds, WAGR tournaments, averages, best round, context splits, par-type and yearly breakdowns, and WAGR position. It also explicitly separates itself from get_my_golf_data by stating 'Son golpes, no hándicap'. An agent can identify the tool without opening anything else.

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 names concrete trigger questions ('su media, su mejor vuelta, cómo rinde fuera o en la última vuelta, sus resultados o su puesto WAGR, o qué ve un entrenador en sus números') and gives an explicit when-not with the alternative to use instead ('para el hándicap, get_my_golf_data'). Both the positive and the exclusion condition are stated outright.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.