Skip to main content
Glama

Tennis Control

Circuitos y categorías

list_circuits
Read-onlyIdempotent

Circuits (federations, international and professional tours) and age categories available, with number of upcoming tournaments.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 the safety profile is fully covered structurally. The description's only added behavioral signal is that entries carry a count of upcoming tournaments, which hints at a bounded, curated result set and a time-relative field. It says nothing about ordering, pagination, or whether the list is static or changes over time, so it adds modest value beyond annotations.

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?

A single dense phrase with zero filler, front-loading the resource and then the qualifiers. It is a fragment rather than a sentence, and the trailing 'with number of upcoming tournaments' clause is slightly compressed, but every word earns its place.

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 no-parameter, read-only enumeration tool with no output schema, the description covers the essential shape of the response: circuits plus age categories plus upcoming-tournament counts. It stops short of explaining the relationship between the two result sets (flat vs nested) or how the counts are scoped, which would matter for an agent parsing the response.

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 and the schema coverage baseline is 4. Nothing is left ambiguous about inputs, and the description correctly adds no parameter talk. No further param explanation is possible or needed.

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?

Names the resource (circuits) and immediately disambiguates the term by parenthesizing what counts as a circuit (federations, international and professional tours), plus states it also returns age categories with upcoming-tournament counts. That is enough for an agent to know it is a reference/enumeration lookup rather than a search. It does not explicitly contrast itself with siblings like list_countries, so it falls short of 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as search_tournaments for finding events. The usage is only implied by the noun phrase describing the returned data. An agent must infer that this is the discovery step for valid circuit/category values.

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