Skip to main content
Glama
Tennis Analytics MCP

Tennis Analytics MCP

get_gsdi_rankings

Read-onlyIdempotent

Rank Grand Slam title campaigns by Grand Slam Dominance Index (GSDI), with optional filters for player, tournament, and result limit.

Instructions

Rank the most mathematically dominant Grand Slam title campaigns using the Grand Slam Dominance Index (GSDI).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
playerNo
tournamentNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds essentially no behavioral context beyond that: it does not explain what GSDI measures, how dominance is computed, whether results are truncated by a default limit, or what happens when an unknown player or tournament is supplied.

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?

It is a single well-formed sentence with the key concept (GSDI) front-loaded and no filler. Brevity here tips into under-specification rather than padding, but structurally there is nothing to cut.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but the tool has three undocumented optional parameters and a bespoke metric (GSDI) that is never defined. For a ranking tool whose entire value depends on understanding what the index means, the description leaves the agent without enough to call or interpret it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so all three parameters (limit, player, tournament) are fully undocumented in the schema. The description does not mention any of them — not the default limit of 15, not that player and tournament act as optional filters, and not whether matching is exact or fuzzy. With zero compensation for a 0% coverage gap, this is a severe deficiency.

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?

The description gives a specific verb ('Rank') and a specific resource ('Grand Slam title campaigns') qualified by a named metric, the Grand Slam Dominance Index (GSDI). It is clear what the tool returns, but it offers no differentiation from the 14 sibling tools (e.g. get_greatness_race, compare_players) which could plausibly also rank players.

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 guidance, no statement of when this is preferable to get_greatness_race or compare_players, and no mention of the filtering options that the schema exposes. The agent must infer the use case entirely from the tool name and the GSDI acronym.

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