Comunio MCP

League table

get_standings

Read-only

Fetch league standings with manager points, squad values, and budget status. Use 'live' period during matchday for real-time points and correct negative budget flags.

Instructions

Get the league table: every manager with their points, squad value and whether their budget is in the red.

Rows come best first, with rank filled in and is_me marking the signed-in manager, and manager_id can be used to look up a rival's squad.

period picks which table. total is the season standings. live is the one to ask for while a matchday is being played: only it fills live_points and players_possibly_scoring, and only it reports negative_budget correctly — under total that flag reads false for everyone, including managers who are actually in the red and will therefore score nothing this matchday.

Read-only: fetches current state and changes nothing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`period`	No		total

Output Schema

TableJSON Schema

Name	Required	Description	Default
`rows`	Yes	Managers, best first
`period`	Yes	Period the table covers, e.g. 'total'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Sep 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint annotation by explaining that the tool changes nothing, which fields only `live` populates, and the surprising caveat that `negative_budget` is unreliable under `total`. This gives the agent important behavioral knowledge that annotations alone do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is detailed yet tightly organized: it opens with the core purpose, then describes row contents, then explains period semantics and the critical caveat, and closes with the read-only guarantee. Every sentence contributes useful operational information without redundancy.

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?

For a single-parameter read-only tool with an output schema, the description is complete: it names the key output fields, explains the parameter's behavior, flags the negative_budget limitation, and confirms no side effects. An agent has everything needed to invoke it correctly.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully compensates by explaining both enum values: `total` is the season standings, while `live` is matchday-aware and correctly reports `negative_budget`. It adds meaning far beyond the bare enum names and default value in the schema.

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?

The description states a specific verb and resource: 'Get the league table' and elaborates exactly what it contains: manager points, squad value, and budget status. It is immediately distinguishable from sibling tools, which concern players, bids, transfers, and squads rather than standings.

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 clearly explains when to use `total` versus `live`, explicitly telling the agent that `live` is the table to request during an in-progress matchday. It does not name alternative sibling tools, but no sibling offers standings, so the period-level guidance is the relevant usage context.

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