Skip to main content
Glama
Sign In
Tennis Evolution

Tennis Evolution

by bobobo2026
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Parse and rank a rally list

rank_highlights
Read-only

Parses a rally list and shows which rallies would be kept, letting you confirm selections before rendering highlight clips.

Instructions

Parse a rally list and show which rallies would be kept, so the user can confirm before rendering.

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

Input Schema

NameRequiredDescriptionDefault
topNoKeep the N best rallies (0 = all; free version caps at 5).
sortNoRanking: longest rally first (hits), longest clip, or chronological.hits
highlights_pathNoPath to a rally list (.txt from sliceapp or .json).
highlights_textNoRally list pasted inline, one rally per line, e.g. '27:14 - 28:08 40 hits'. Use either this or highlights_path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe non-mutating operation, and the description is consistent with that, framing it as a preview that selects rallies without side effects. It adds no further behavioral detail such as what the preview returns (list vs. counts), how the free-version cap at 5 is surfaced, or whether ties/zero-rally results have special handling.

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 front-loaded sentence with no filler; the purpose and the reason for it are packed into one clause. It is efficient but leaves no room for the output or cap context that would make it self-sufficient.

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

Completeness3/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 carries the burden of explaining what the preview actually returns, and it does not — an agent cannot tell whether the result is a filtered rally list, per-rally scores, or just a count. That gap matters for a tool whose entire value is the preview output, even though the input schema is fully documented.

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

Parameters3/5

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

Schema description coverage is 100%, so top, sort, highlights_path, and highlights_text are all documented in the schema, including the free-version cap and path/inline alternatives. The description adds nothing about parameters, so the baseline 3 applies.

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+resource ("Parse a rally list") and adds the twist that it only shows which rallies would be kept, which differentiates it from the rendering sibling start_highlight_reel implied by "before rendering." It stops short of naming that sibling explicitly, so the distinction is inferred rather than stated.

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

Usage Guidelines3/5

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

"so the user can confirm before rendering" implies this is a preview/dry-run step that precedes start_highlight_reel, which is useful usage context. But it never names the alternative tool nor states when this step can be skipped or when it is mandatory, leaving the workflow routing implicit.

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

Deploy Server

Other Tools