Adios: Croatian news

Weekly summary

get_weekly_digest

Read-onlyIdempotent

Adios's written summary of a week (Monday-Sunday) in Croatia: the most important stories, by section, with links. Pass any date of the week, or nothing for the latest; croatia_only=true leaves out the world section and its stories.

Input Schema

Name	Required	Description	Default
`date`	No	Any day of the week (YYYY-MM-DD); default the newest.
`croatia_only`	No	Croatia only: without the world section and its stories, as "Samo Hrvatska" on adios.hr (default: all news).

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 11, 2026

addedInput schema / properties / croatia_only

Added value: +{
+  "description": "Croatia only: without the world section and its stories, as \"Samo Hrvatska\" on adios.hr (default: all news).",
+  "type": "boolean"
+}

First observedOct 11, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true), and the description adds that output is 'written summary...with links' and the time window Monday-Sunday. It does not disclose pagination, rate limits, or return format details beyond what the output schema likely provides.

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?

A single dense sentence with zero waste, front-loading the core purpose and time window before the parameter behavior. Every clause earns its place.

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?

Complete for a read-only digest tool with an output schema and full parameter coverage. The description supplies the domain-specific context (Croatia weekly summary) an agent needs to route correctly, though it does not detail the return structure.

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 both parameters fully. The description restates the date and croatia_only semantics but adds no syntax or format details beyond the schema baseline.

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 (get), resource (weekly digest), and distinctive scope (Croatia, Monday-Sunday) that clearly separates it from siblings like get_daily_digest and get_latest_news. The mention of 'by section, with links' further specifies the content shape.

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?

Explains when to use croatia_only=true and that passing nothing returns the latest, but does not explicitly name alternatives (e.g., get_daily_digest for daily coverage). The usage context is clear without naming competitors.

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?