Skip to main content
Glama
ProjectMakersDE

horizOn MCP Server

Official
by ProjectMakersDE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get News

horizon_get_news
Read-onlyIdempotent

Retrieve published in-game news, announcements, and patch notes from the horizOn dashboard for display in a game's news feed or message of the day, filterable by language.

Instructions

Lists the published in-game news of the app (announcements, patch notes) created in the horizOn dashboard, newest first. Use when: a game shows a news feed or a message of the day, optionally filtered to the player's language. Not for: configuration values (use horizon_get_remote_config) or UI translations (use horizon_get_localization). Side effects: None (read only). Returns: an array of {id, title, message, releaseDate, languageCode} with only published entries whose release date has passed; an empty array means there is no news. Without languageCode, entries of all languages are returned. Errors: Needs HORIZON_API_KEY. Every failure returns an error result (isError) with the HTTP status and body: a 401 that horizon_test_connection also returns means HORIZON_API_KEY is wrong, 429 means the account's per-minute rate limit was reached (wait a minute, then retry).

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of entries to return, 0 to 100 (default 20)
languageCodeNoISO 639-1 code (2 lowercase letters, for example 'en' or 'de') to return only entries in that language. Omit for all languages

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.6.0
    • changedInput schema / properties / languageCode / description
      Previous value: -"ISO 639-1 language code (2 characters, e.g. 'en')"New value: +"ISO 639-1 code (2 lowercase letters, for example 'en' or 'de') to return only entries in that language. Omit for all languages"
    • changedInput schema / properties / limit / description
      Previous value: -"Number of news items to return (0-100, default 20)"New value: +"Maximum number of entries to return, 0 to 100 (default 20)"
  2. First observedv1.5.4

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing auth requirements (HORIZON_API_KEY), filtering behavior (only published entries past release date), empty-array semantics, and detailed error semantics: 401 means a bad key (cross-referenced to horizon_test_connection) and 429 means a per-minute rate limit with a retry instruction. This is exactly the extra context annotations don't carry.

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?

Front-loaded with purpose, then cleanly labeled sections (Use when / Not for / Side effects / Returns / Errors). The length is justified because each section carries decision-relevant information for an agent with no output schema to fall back on.

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 compensates by specifying the return shape ({id, title, message, releaseDate, languageCode}), field semantics, and empty-result meaning. Auth, side effects, and error handling are all covered, so an agent has everything needed to invoke and interpret the call.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description reinforces the languageCode filtering meaning ('optionally filtered to the player's language', all languages when omitted), which adds contextual clarity, though it adds no syntax detail for limit beyond what the schema already documents.

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?

States a specific verb and resource ('Lists the published in-game news... announcements, patch notes'), adds ordering ('newest first'), and explicitly distinguishes itself from siblings horizon_get_remote_config and horizon_get_localization. An agent can identify the tool's scope without opening the schema.

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?

Provides an explicit 'Use when' condition (a game shows a news feed or message of the day, optionally language-filtered) and an explicit 'Not for' with the correct alternative named for each exclusion. Nothing is left to inference.

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

Deploy Server

Other Tools