Adios: Croatian news

Article

get_article

Read-onlyIdempotent

Full details of one news article by id: Adios's neutral summary and background context, topics and named entities, the same news on other portals, related articles, the location on the map, the followed story (timeline) it is part of, and its signals and badges (urgent, big, world, clickbait, sponsored). Use after get_latest_news, search_news or get_nearby_news to explain a story.

Input Schema

Name	Required	Description	Default
`id`	Yes	The article's id (from a list or a search).

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	No	count, plan, include_filler, the limits applied (e.g. radius_limited_to), and for a nearby search its center.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

addedOutput schema / properties / data / properties / signals / properties / world_event

Added value: +{
+  "pattern": "^-?(?:0|[1-9]\\d*)(?:\\.\\d+)?(?:[eE][+-]?\\d+)?$",
+  "type": [
+    "string",
+    "number",
+    "null"
+  ]
+}

Changed2 schema fields changedOct 12, 2026

addedOutput schema / properties / data / properties / badges

Added value: +{
+  "default": null,
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedOutput schema / properties / data / properties / signals

Added value: +{
+  "default": null,
+  "properties": {
+    "clickbait": {
+      "pattern": "^-?(?:0|[1-9]\\d*)(?:\\.\\d+)?(?:[eE][+-]?\\d+)?$",
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "importance": {
+      "pattern": "^-?(?:0|[1-9]\\d*)(?:\\.\\d+)?(?:[eE][+-]?\\d+)?$",
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "in_croatia": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "sponsored": {
+      "pattern": "^-?(?:0|[1-9]\\d*)(?:\\.\\d+)?(?:[eE][+-]?\\d+)?$",
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    },
+    "urgency": {
+      "pattern": "^-?(?:0|[1-9]\\d*)(?:\\.\\d+)?(?:[eE][+-]?\\d+)?$",
+      "type": [
+        "string",
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

First observedOct 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds substantive context by disclosing exactly what depth of data is retrieved—neutral summary, background, cross-portal coverage, timeline, and badges—which goes beyond the annotations.

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?

Front-loaded with the core purpose, then a dense but purposeful enumeration of return facets and a routing sentence. The list of returned items is long, but each item is informative rather than filler.

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 read-only single-resource lookup with full schema coverage, an output schema, and clear annotations, the description covers what an agent needs: what it returns, its id input, and where it fits in the toolchain. No meaningful gaps remain.

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 the single 'id' parameter is documented there as coming 'from a list or a search.' The description's phrase 'by id' adds no syntax or format detail beyond the schema, 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?

States a specific verb and resource ('Full details of one news article by id') and enumerates the returned facets (summary, topics/entities, other portals, related articles, map location, timeline, signals/badges). It clearly distinguishes this single-article enrichment tool from the list/search siblings it names.

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?

Explicitly says to use it 'after get_latest_news, search_news or get_nearby_news to explain a story,' which names concrete upstream tools and the intent. It lacks an explicit when-not-to-use (e.g. don't use for browsing) but the routing context is strong.

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

All Adios: Croatian news 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?