Skip to main content
Glama

Tennis Control

Ficha de un torneo

get_tournament
Read-onlyIdempotent

Full public details of one tournament by its id (from search_tournaments): dates, venue, categories, entry and withdrawal deadlines, entry rule and official link.

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

Input Schema

NameRequiredDescriptionDefault
idYesTournament id returned by search_tournaments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety and repeatability are covered by structured data. The description adds that these are public details plus a field inventory, which is useful, but says nothing about behavior for an invalid or unknown id.

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?

A single front-loaded sentence with the resource and identifier first, then a compact field list. No filler, no repetition of the title.

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 one-parameter read lookup with no output schema, the enumerated fields are exactly the return-value information an agent needs. The only remaining gap is error/not-found behavior, which is minor for this tool's complexity.

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?

Schema coverage is 100% and the single id parameter is fully described there. The description still adds provenance meaning by tying the id to search_tournaments output, telling the agent where a valid value comes from rather than just its type.

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 ('Full public details of one tournament by its id') and enumerates what those details comprise: dates, venue, categories, entry/withdrawal deadlines, entry rule, official link. This clearly separates it from search_tournaments, which only locates tournaments.

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?

The parenthetical '(from search_tournaments)' establishes the intended workflow: find ids via search, then fetch full details here. It gives clear context for when to call it, but offers no explicit exclusions (e.g., what to use if the id is unknown or if a list view is wanted).

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.

Resources