Skip to main content
Glama

Get my tournaments

get_my_tournaments
Read-onlyIdempotent

Sus últimos torneos del historial oficial (federación), del más reciente al más antiguo: vueltas, total al par, su puesto si el WAGR lo tiene, y su propia nota de cada uno (puesto que él cuenta, cómo se sintió, lo mejor del torneo, y si es pública). Úsala cuando hable de un torneo reciente. Tras un torneo, antes del resultado, pregúntale qué tal le fue y cómo se sintió; luego ofrécele guardarlo con save_tournament_note.

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_tournaments"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the data originates from official federation history, results are ordered newest-first, and entries may carry the user's own private-or-public notes. It does not state how many tournaments are returned or any pagination/limit behavior.

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 resource and ordering, then the field list, then usage guidance — a sensible structure. Some phrasing is loose ('puesto que él cuenta', 'lo mejor del torneo'), and the field enumeration plus workflow instructions make it longer than strictly needed, but no sentence is pure filler.

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?

With no output schema, the description correctly carries the burden of explaining what comes back (rounds, score to par, WAGR position, personal notes) — that is the right call. The only real gap for a list-style retrieval tool is the absence of any statement about result count, recency window, or what happens when no tournaments exist.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The schema's additionalProperties:false is consistent with a parameterless call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('sus últimos torneos del historial oficial') plus the source (federación) and ordering (del más reciente al más antiguo), and enumerates what each entry contains. It never names the closest sibling (get_my_competitions), so an agent must infer the boundary, but the scope of this tool is otherwise unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete trigger ('Úsala cuando hable de un torneo reciente') and even a conversational workflow: ask how the round went before showing results, then offer save_tournament_note. That routes the agent to a sibling tool for the follow-up action. Missing an explicit when-not-to-use or a contrast with get_my_competitions.

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.