Skip to main content
Glama

Padel Analyst

show-player-audience

Read-onlyIdempotent

Get the popularity of a player among padel fans by providing their player ID (Padel Fan Index), measured over a window (last 12 months by default). Returns fan_share (percentage of fan interest that went to the player), popularity_rank (position by fan_share), popularity_index (fan interest against the interest expected for the player's level, 1.0 = as expected, 2.0 = twice), fan_share by month and its trend (rising, stable or declining). Every value is relative to the rest of the circuit, never an absolute fan count. To get the player ID, use the "search-players" tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "player_id": "<player_id>"
    },
    "name": "show-player-audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
player_idYesThe ID of the player to get the audience for.
after_dateNoStart of the window (YYYY-MM-DD). Defaults to 12 months before before_date.
before_dateNoEnd of the window (YYYY-MM-DD). Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the crucial caveat that every value is relative to the rest of the circuit and never an absolute fan count. That prevents a common misinterpretation of the returned numbers and is genuine context beyond the 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?

Front-loaded with the purpose and metric, followed by return-field semantics and the prerequisite tool. It is dense and every sentence carries information, though the long single block could be split for easier scanning.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so thoroughly: fan_share, popularity_rank, popularity_index with its 1.0/2.0 interpretation, monthly series, and trend categories. Combined with the relative-value caveat, an agent has everything needed to call and interpret it.

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 all three parameters are already documented in the schema, including the defaults for after_date and before_date. The description only restates the default window, adding no syntax or format detail beyond the structured fields, so the baseline of 3 applies.

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 ('Get the popularity of a player among padel fans') and names the proprietary metric (Padel Fan Index) plus its default window. This is clearly distinguishable from siblings such as show-player-stats or show-player-form, which measure performance rather than audience interest.

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

Usage Guidelines4/5

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

Explicitly routes the agent to 'search-players' to obtain the required player_id, which is the main usage prerequisite. It does not explicitly exclude or compare against the other player-oriented siblings, but the metric definition makes the appropriate context clear.

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