Adios: Croatian news

Latest news

get_latest_news

Read-onlyIdempotent

Latest Croatian news from all major portals (deduplicated: one item per news story, with how many portals covered it). Filter by category (crime, politics, sport, economy, world, show, …), portal slug, or period (from/to). Use sort=most_covered for the biggest stories of the moment, most_read for what people read, badge=breaking for what is urgent or big in Croatia and the major world events (or one badge: urgent, big, world, clickbait, sponsored). Returns title, description, Adios URL, source portal and its URL, time, categories, and signals (0-1: urgency, importance, world_event, clickbait, sponsored; in_croatia) with badges (urgent, big, world, clickbait, sponsored) for what to flag.

Input Schema

Name	Required	Description
`to`	No	To (YYYY-MM-DD or ISO time).
`from`	No	From (YYYY-MM-DD or ISO time), within the plan's archive.
`sort`	No	newest (default), most_read or most_covered (most portals).
`badge`	No	Only stories with a badge: breaking (urgent, big and world together, as on Udarne vijesti), urgent, big, world, clickbait, sponsored.
`limit`	No	How many results (default 20, at most what the plan allows).
`offset`	No	Skip this many (paging).
`category`	No	Category: crime, politics, sport… (see /v1/categories).
`provider`	No	Only one portal, by its slug (see /v1/providers).
`stories_only`	No	Only news that is part of a followed story (timeline).
`include_filler`	No	Filler (horoscopes, quizzes, reality shows, celebrity gossip, promos) is left out of every list; true brings it back.

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.

Changed2 schema fields changedOct 13, 2026

addedInput schema / properties / badge

Added value: +{
+  "description": "Only stories with a badge: breaking (urgent, big and world together, as on Udarne vijesti), urgent, big, world, clickbait, sponsored.",
+  "enum": [
+    "breaking",
+    "urgent",
+    "big",
+    "world",
+    "clickbait",
+    "sponsored"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / data / items / 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 / items / properties / badges

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

addedOutput schema / properties / data / items / 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/5.0

Behavior4/5

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

Annotations already establish the safe read-only/idempotent profile, so the description only needs to add context, and it does: deduplication semantics, filler exclusion by default, archive scoping ('within the plan's archive'), and plan-capped result limits. These are genuine behavioral traits an agent couldn't infer from the annotations, though pagination/output behavior is not elaborated.

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

Conciseness3/5

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

Purpose and filters are front-loaded, but the second sentence is a dense run-on that enumerates return fields ('title, description, Adios URL, source portal...') already defined by the output schema, adding length without new decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter read tool with full schema coverage, output schema, and rich annotations, the description covers filtering intent, default exclusions, and plan limits adequately. Only secondary details like paging interaction or the precise meaning of overlapping signals/badges are left implicit.

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 description coverage is 100% and three enums are self-documented, so the baseline is 3. The description largely restates schema content (badge=breaking equating urgent+big+world, sort modes) rather than adding syntax, format, or interaction detail beyond it.

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 ('latest Croatian news from all major portals') plus a differentiating scoping trait – deduplication to one item per story with coverage counts. An agent can distinguish this recency/aggregation tool from search_news, get_article, or get_city_news without opening a schema.

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?

Gives concrete intent-to-parameter mappings ('Use sort=most_covered for the biggest stories of the moment, most_read for what people read, badge=breaking for what is urgent'), which tells the agent when to reach for which knob. It never names an alternative sibling or states when NOT to use this tool, so it stops short of a 5.

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?