Skip to main content
Glama

A city's news

get_city_news
Read-onlyIdempotent

The last 30 days of news of a Croatian city and its surroundings (Zagreb, Split, Rijeka, Osijek, Zadar, Pula, Slavonski Brod, … ~40 cities), newest first, each with place and distance from the city centre. Pass the city name or slug.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_city_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe city: zadar, split, slavonski-brod… or its name.
kindsNoKinds of map stories, e.g. fire,crash,crime (see /v1/categories).
limitNoHow many results (default 30, at most what the plan allows).
include_fillerNoFiller (horoscopes, quizzes, reality shows, celebrity gossip, promos) is left out of every list; true brings it back.

Output Schema

NameRequiredDescriptionDefault
dataYes
metaNocount, 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.

  1. Changed1 schema field changed
    • changedInput schema / properties / kinds / items / enum
      Previous value: -[
      -  "waste",
      -  "fire",
      -  "fire-out",
      -  "crash",
      -  "crime",
      -  "explosion",
      -  "quake",
      -  "flood",
      -  "storm",
      -  "rescue",
      -  "missing",
      -  "protest",
      -  "politics",
      -  "economy",
      -  "sport",
      -  "culture",
      -  "world",
      -  "other"
      -]New value: +[
      +  "waste",
      +  "fire",
      +  "fire-out",
      +  "crash",
      +  "crime",
      +  "explosion",
      +  "attack",
      +  "quake",
      +  "flood",
      +  "storm",
      +  "rescue",
      +  "missing",
      +  "protest",
      +  "politics",
      +  "economy",
      +  "sport",
      +  "culture",
      +  "world",
      +  "other"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: a 30-day window, newest-first ordering, and returned place/distance fields.

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?

The description is front-loaded with time window, geography, ordering, and return-field details. The long city parenthetical is justified by demonstrating coverage, and the final instruction is short and useful.

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 rich annotations, an output schema, and full schema description coverage, the description supplies the important context an agent needs: Croatian-city scope, 30-day window, newest-first ordering, and result fields. It is only slightly incomplete in not routing against nearby/latest/search alternatives.

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 all four parameters, including the kinds enum and filler behavior. The description adds city examples and the name-or-slug instruction, but much of that repeats the schema and it does not deepen semantics for kinds, limit, or include_filler.

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?

The description states a specific resource and scope: last 30 days of Croatian city news, newest first, with place and distance from the city centre. It is clear what the tool returns, but it does not explicitly distinguish itself from siblings such as get_nearby_news or get_latest_news.

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?

The scope implies when to use it for a specific Croatian city, but there is no explicit when/when-not guidance and no named alternative such as get_nearby_news, get_latest_news, or search_news. The instruction 'Pass the city name or slug' is a parameter hint rather than usage routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.