Skip to main content
Glama

Нишка – отворен слой

Какво се промени (Пловдив)

plovdiv_changes
Read-onlyIdempotent

Item-level changes Nishka saw in Plovdiv's official sources since a date — municipal notices, road works, ВиК water interruptions and Основа facts — newest first, with the source URL of each. Use it to keep an agent's own data current.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plovdiv_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindsNo
limitNo
sinceNoYYYY-MM-DD or an ISO time; default 7 days ago.

Output Schema

NameRequiredDescriptionDefault
countYes
sinceYes
changesYes
citationsYesEvery source the result rests on. Cite url; give checkedOn or publishedOn.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kinds / items / enum
      Previous value: -[
      -  "notice",
      -  "road",
      -  "outage",
      -  "fact"
      -]New value: +[
      +  "notice",
      +  "road",
      +  "outage",
      +  "fact",
      +  "contact"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / citations / items / properties / licence / enum
      Previous value: -[
      -  "CC-BY-4.0",
      -  "official-record"
      -]New value: +[
      +  "CC-BY-4.0",
      +  "official-record",
      +  "ODbL-1.0"
      +]
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds ordering ('newest first') and per-item source URLs, plus the domain boundary of Plovdiv official sources. It does not discuss result volume, the 200-item cap, or what happens when nothing changed in the window.

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?

A single dense sentence with the resource and scope front-loaded and the use case appended last; no filler. It is long but each clause carries distinct information (granularity, geography, source type, ordering, provenance, purpose).

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

Completeness3/5

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

With three optional parameters, an output schema, and strong annotations, the description is adequate but not complete. Gaps remain around the `limit` parameter, default behavior when `kinds` is omitted, and the meaning of 'Nishka' as the observing agent, all of which an agent would need to call this confidently for the first time.

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 coverage is only 33% — just `since` is documented — so the description must compensate, and it partially does by naming the content categories that map onto the `kinds` enum (notice, road, outage, fact). It says nothing about `limit` (1–200), its default, or that `kinds` may be omitted to mean all types, and the `contact` enum value is unmentioned.

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 verb and resource: 'item-level changes ... in Plovdiv's official sources since a date', and enumerates the concrete content types (municipal notices, road works, ВиК water interruptions, Основа facts). An agent can tell this is a change-feed tool, distinct from record lookups like plovdiv_place_record. The unexplained actor 'Nishka' adds a small ambiguity but does not obscure the purpose.

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?

It gives one implied usage context: 'Use it to keep an agent's own data current', which points at incremental-sync scenarios. There is no explicit when-not-to-use guidance and no named alternative (e.g., when to prefer the place-record or document tools for a single lookup). Usage is implied rather than routed.

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.

Resources