Skip to main content
Glama
Sign In

VoxBall · the fans' verdict

by app.voxball
OverviewDiscussionsAdmin

Best player of the season, elected by those who watch

get_season_ranking
Read-onlyIdempotent

The VoxBall ranking of the best player of the season, all competitions: each match gives points to its top 10, from the fans' verdict when fans voted, otherwise from the press and rating algorithms. Returns the ranking with its electorate (voters, VoxBall members), whether the season is still in progress, and the page to link.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10.
seasonNoe.g. "2026-27". Default: the current season.
languageNoLanguage of the answer sentence and of the page links. Default: en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent read, so the description adds genuine value by disclosing the point-scoring methodology (top-10 per match, fan verdict vs. press/algorithms) and what the payload includes: electorate, in-progress status, and page link. Minor gap: no pagination or size expectations beyond the limit default.

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?

Two dense sentences with the resource and scope front-loaded, followed by the return contents. Every clause carries information, though the methodology sentence is long enough to slow parsing slightly.

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

Completeness4/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 does the necessary work of explaining return contents (ranking plus electorate, season status, page link). Combined with the annotations covering safety and the fully documented schema, an agent has enough to call it correctly.

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%, with defaults and the language enum fully documented in the schema. The description adds no parameter-level meaning such as season format or limit behavior, 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?

The description names the specific resource ('VoxBall ranking of the best player of the season, all competitions') and explains the scoring basis, so an agent knows exactly what data this returns. It does not explicitly differentiate from siblings like get_match_verdict, though the resource itself is clearly distinct.

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?

Usage is only implied by the resource description — an agent can infer this is the tool for season-wide player rankings. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative for per-match data.

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

All VoxBall · the fans' verdict toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources