Skip to main content
Glama
Tennis Analytics MCP

Tennis Analytics MCP

get_nail_biters

Read-onlyIdempotent

Rank dramatic Grand Slam finals and semifinals by Nail-Biter Index, with optional filters for player, tournament, or tag.

Instructions

Find the highest-drama Grand Slam Finals & Semifinals using the Nail-Biter Index (NBI).

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

Input Schema

NameRequiredDescriptionDefault
tagNo
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 establish that this is a read-only, idempotent, non-destructive lookup, so safety is covered. The description adds little beyond that: it does not explain what NBI measures, how results are ordered, or what 'highest-drama' means operationally.

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 front-loaded sentence with no wasted wording. The main weakness is that its central term, the Nail-Biter Index, is unexplained jargon rather than useful compression.

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?

The output schema and annotations reduce some burden, but the description is still thin for a four-parameter filtering tool with 0% schema description coverage. It leaves the agent without sufficient guidance on parameters, ranking behavior, or result semantics.

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?

The schema has four parameters (tag, limit, player, tournament) with 0% description coverage, and the description mentions none of them. An agent gets no guidance on what tag means, how player or tournament filtering works, or how limit affects ranking results.

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 (Find) and a specific resource scope (Grand Slam Finals & Semifinals), plus a ranking concept (NBI). It is distinguishable from broader siblings like search_matches, though the key term NBI is left undefined.

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?

It implies this is for finding dramatic major matches, but gives no explicit when-to-use guidance, no exclusions, and no routing advice relative to search_matches or other match-oriented siblings.

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