Comunio MCP

League news

get_news

Read-only

Fetch the league news feed for announcements, member joins, resets, lineup changes, and transfer activity. Filter by type and limit to see what changed and why.

Instructions

Get the league news feed, newest first: what has happened in this community.

Announcements from Comunio and from the community admin, members joining, the league being reset, lineups being changed, and transfer rounds settling. Use it to answer "what has been going on" or to find out why something changed — a reset, a rule change or a new member explains a lot that the squad and market do not.

Each entry has a type. The ones seen so far are SYSTEM_ADMINISTRATION (Comunio's own announcements, such as when a matchday starts), COMMUNITY_ADMINISTRATION (the admin resetting or reconfiguring the league), MEMBER_ADMINISTRATION (someone joining), LINEUP_CHANGED and TRANSACTION_TRANSFER. It is an open set, so treat an unfamiliar one as news rather than an error.

On administration entries the whole announcement is in title and text is null. Read title first and treat it as content, not as a label.

For transfer entries this gives only how many moves there were. Use get_transfers for the players, the prices and who was on each side — it parses the same entries properly.

types filters to the kinds asked for, matched case-insensitively; leave it out to get everything. limit caps how many entries come back, one page by default, and a larger value costs one extra request per page.

Read-only: fetches the feed and changes nothing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`types`	No

Output Schema

TableJSON Schema

Name	Required	Description
`entries`	Yes	Newest first
`summary`	Yes
`has_more`	Yes	Whether older entries exist beyond what was fetched

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Sep 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses substantial behavior: newest-first ordering, an open set of entry types, null 'text' on administration entries, transfer entries containing only counts, and the per-page request cost of larger limits. This is far more than annotations alone provide.

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?

The description is longer than necessary for a simple feed tool, but the length is justified by the non-obvious type semantics, null-field behavior, transfer-vs-get_transfers distinction, and per-page cost. It is front-loaded with the core purpose and organized into clear sections. Slight redundancy exists around read-only behavior, but otherwise every sentence earns its place.

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?

Given the output schema exists, the description does not need to spell out return shape. It covers purpose, usage, parameter semantics, type behavior, edge cases, alternatives, and the read-only safety profile. An agent has everything needed to invoke and interpret results 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%, so the description carries the full burden for the two parameters. It explains that 'types' filters case-insensitively and can be omitted for everything, and that 'limit' caps entries with a default page and an extra-request cost. It also documents the known type values.

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 opens with a specific verb and resource: 'Get the league news feed, newest first' and immediately states what it contains. It also differentiates itself from get_transfers by explicitly saying transfer entries only give move counts and that get_transfers parses them properly.

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?

It tells the agent when to use this tool ('what has been going on', 'find out why something changed') and explicitly routes transfer-related detail to get_transfers. It also gives concrete guidance on types and limit, including when to omit them.

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