Skip to main content
Glama

The Tennis Desk

A league table

query_league_standings
Read-onlyIdempotent

Builds the Desk's league table for a team's flight, with the named team's place, which it ranks from recorded results by the league's own rule and tie-breaks. Call it for the standings, how a team finished, who won the league or 'the table'. Pass the team name, or nothing for the member's own team. For a whole league, pass league and area instead, such as "55 & over men's 8.0" and 'Marin'. Never pass a club or an area as the team.

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

Input Schema

NameRequiredDescriptionDefault
areaNoThe area of that league, as the Desk names it, e.g. 'Marin' or 'San Francisco'. Used only with `league`.
teamNoTeam or club name whose league table to build, e.g. 'Belvedere' or 'Belvedere mixed 8.0'. Omit to use the signed-in member's own team, or to ask by `league`. Or the team's Desk page link or number.
askedNoThe person's question word for word, never paraphrased. Leave it out rather than invent one.
leagueNoA league to build the table of when no team is named, with every league word the question gives, the age group included: its name, e.g. 'Adult 55 & Over Mens 8.0', or its words, e.g. "55 & over men's 8.0" or "women's combo 6.5 daytime". Used only without `team`.
seasonNoLeague year, e.g. 2025. Defaults to the current season.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely non-structured behavior: the ranking rule (league's own rule and tie-breaks) and the season default to the current season. It stops short of describing the table's contents or row limits.

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?

Front-loaded with the core action before the routing and constraint details, and no filler sentences. Some sentences are long and the trailing club/area warning reads as an afterthought rather than integrated guidance.

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

Completeness5/5

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

With five optional params and no output schema, the description covers both invocation modes, the default team, the season default, and the ranking basis — enough for an agent to call it correctly without guessing. Return-shape detail is the only minor omission, and it partly gestures at it via "with the named team's place."

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%, so baseline is 3, but the description adds real semantics: omitting `team` falls back to the member's own team, `league`/`area` are an alternate mode, and `asked` should be verbatim. One tension: it says never pass a club as `team`, while the schema's own example is 'Belvedere', a club name.

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 ("Builds the Desk's league table for a team's flight") plus the scope of what it returns (the named team's place). "Ranks from recorded results by the league's own rule and tie-breaks" implicitly separates it from projection siblings like project_standings and record siblings like query_team_record.

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

Usage Guidelines5/5

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

Gives explicit invocation triggers ("for the standings, how a team finished, who won the league or 'the table'") and an explicit alternative mode ("For a whole league, pass `league` and `area` instead"). It also names an exclusion: "Never pass a club or an area as the team."

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