Adios: Croatian news

Search

search_news

Read-onlyIdempotent

Search Croatian news by meaning (semantic + text). Write the query in Croatian when you can (e.g. "požar Split", "izbori", "cijene goriva"); English works too. Optional category, portal, period and badge (breaking, urgent, big, world, clickbait, sponsored). Returns matching articles, newest-relevant first, each with its signals and badges (urgent, big, world, clickbait, sponsored).

Input Schema

Name	Required	Description
`q`	Yes	The question, e.g. "požar Split" or "inflation".
`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	relevance (default) or newest.
`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.
`category`	No	Category: crime, politics, sport… (see /v1/categories).
`provider`	No	Only one portal, by its slug (see /v1/providers).
`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

A3.5/5.0

Behavior3/5

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

Annotations already carry the full safety profile (readOnly, idempotent, openWorld=false, non-destructive). The description adds genuine behavioral context beyond that: results are 'newest-relevant first' and each carries signals and badges. It stops short of noting default limits, pagination, or archive constraints, so it is solid but not rich.

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?

Three tight sentences, front-loaded with the core 'search by meaning' statement followed by language guidance and the filter enumeration. Little waste, though the badge list appears twice (query filter and return values), which is mildly redundant.

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?

With an output schema present and 100% schema coverage, the description need not explain return values, and it correctly focuses on language guidance and filtering. It is nearly complete for a search tool, missing only ordering/pagination clarification relative to the sort parameter.

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%, so every one of the ten parameters is already documented in the schema, including enum meanings for badge and category. The description restates the same filter list and adds only example query strings, which the schema's 'q' description also provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search Croatian news by meaning (semantic + text)'), which already distinguishes it from listing tools like get_latest_news. It does not, however, explicitly contrast itself with the sibling 'search' or 'research_topic', so sibling differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides useful invocation guidance ('Write the query in Croatian when you can... English works too') and enumerates the optional filters, but never states when to prefer this over sibling search, research_topic, or get_latest_news. Usage context is implied rather than explicit.

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?