horizon_get_newsRetrieve news articles from horizOn for game or app projects, with optional ISO language filtering to target specific audiences.
Gets news articles from horizOn with optional language filtering.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of news items to return (0-100, default 20) | |
| languageCode | No | ISO 639-1 language code (2 characters, e.g. 'en') |
Changes observed during successful MCP inspections.
v1.5.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden, yet it only says 'gets'. It omits whether authentication is required, how results are ordered or paginated, and what happens when no news exists — meaningful gaps for a network-backed read tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no wasted words. It is efficient, though it could carry one more clause of useful context without becoming bloated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter, optional-args read tool with no output schema, the description is minimally viable but leaves out auth requirements, result ordering, and pagination behavior that an agent would want before calling it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so both limit and languageCode are fully documented in the schema (range, default, ISO 639-1 format). The description's mention of optional language filtering adds nothing beyond that, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb ('Gets') and resource ('news articles from horizOn') plus the scope of filtering. No sibling tool retrieves news, so differentiation is implicit, but the purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this tool, when not to, or which alternatives exist. Nothing indicates whether it requires authentication or how it relates to the other horizOn read tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.