Adios: Croatian news

Everything connected

research_topic

Read-onlyIdempotent

The research tool: give a free question (person, place, event, topic) and get EVERYTHING connected in one call: matching articles, followed stories (multi-day timelines with stages), map locations, the daily summaries that covered it, and a single chronological timeline. Best first call for "what happened with X" or "explain the story of X".

Input Schema

Name	Required	Description
`q`	Yes	What you want to know: a person, a place, an event, a topic.
`days`	No	How many days back (default 30, at most the plan's archive).
`limit`	No	How many results (default 15, at most what the plan allows).
`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.

Changed1 schema field changedOct 13, 2026
- addedOutput schema / properties / data / properties / articles / 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 / properties / articles / items / properties / badges

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

addedOutput schema / properties / data / properties / articles / 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.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuine behavioral value by disclosing that this is a broad fan-out aggregation returning five distinct result kinds in one call, which is not inferable from the annotations alone.

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 tool's identity, then the input and the enumerated outputs, closing with a crisp usage hook. The output enumeration is dense but each item earns its place by distinguishing the aggregation scope; only the colon-heavy list slightly slows reading.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. The description supplies the aggregation semantics and a use-case trigger; what remains missing is any hint that results are bounded by plan archive/limits, though the schema covers that.

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 the schema already documents q, days, limit, and include_filler. The description restates the query semantics (person, place, event, topic) but adds no syntax or format detail beyond the schema, so 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?

Names a specific verb (research) and resource (topic/question) and enumerates the aggregated result types (articles, stories, map locations, daily summaries, timeline), which clearly separates it from single-purpose siblings like get_story_timeline or search_news.

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?

"Best first call for 'what happened with X'" gives clear positive routing guidance for when to reach for this tool over the narrower siblings. It stops short of naming a specific alternative to use instead when a narrower call is preferable, so it is not a full when/when-not statement.

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?