VoxBall · the fans' verdict

Man of the match, voted by fans

get_match_verdict

Read-onlyIdempotent

The VoxBall verdict of one match: who is the man of the match according to the fans who voted, with what qualifies it (number of voters, how many are VoxBall members, which club the other voting supporters follow, provisional or not, date), the top 10, and the number one of the press and of rating algorithms for comparison. Same verdict as the public match page.

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": {
      "match_id": "<match_id>"
    },
    "name": "get_match_verdict"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Language of the answer sentence and of the page links. Default: en.
`match_id`	Yes	From search_matches, or the number at the end of a VoxBall match page address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real substance beyond that: the verdict is fan-sourced, carries qualifiers (voter count, member count, rival supporters' club, provisional flag, date), and includes top 10 plus press and algorithm number ones for comparison. It does not mention freshness/caching or failure modes such as a match with no votes yet.

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?

One long but tightly packed sentence: the core purpose comes first, then the qualifying fields, then the comparison data. The parenthetical enumeration is dense yet each item conveys a distinct returned field, so it earns its space; minor readability cost from the nested list.

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 no output schema, the description carries the burden of describing return content, and it does so thoroughly — the voter-derived verdict, its qualifiers, the top 10, and the press and rating-algorithm leaders. Nothing essential about calling or interpreting the result is left out for a two-parameter read tool.

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 coverage is 100% and both parameters are already well documented in the schema, including the origin of match_id and the default for language. The description adds no meaning about either parameter, so the baseline 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?

Names a specific resource (one match's fan-voted man of the match) and a specific verb-frame ('the verdict of one match'), and enumerates what that verdict contains. It is clearly distinct from get_season_ranking (season-wide) and search_matches (which supplies the match_id).

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?

The description implies when to reach for it (you already have a single match in hand, and match_id comes from search_matches or a VoxBall match URL) and frames it as the same verdict shown on the public match page. It does not state any exclusion or when-not-to-use case, so it stops short of a 5.

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 tools Inspect

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

Need Help?