Skip to main content
Glama

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

Досие на адреса (Пловдив)

plovdiv_place_record
Read-onlyIdempotent

What is known now about one Plovdiv street or quarter: planned water interruptions, road works and traffic changes, municipal notices, city council decisions naming it, the paid parking zone of a street, everyday places nearby, and notices no longer published — each with its source URL and dates. Accepts a street („бул. Цар Симеон“), a quarter („Кършияка“), a local name („Кючука“, „Джумаята“) or a Тракия block („Тракия, бл. 14“). Bulgarian input works best.

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": {
      "place": "<place>"
    },
    "name": "plovdiv_place_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesA Plovdiv street, quarter, local name or landmark, in Bulgarian.

Output Schema

NameRequiredDescriptionDefault
keyYes
urlYes
kindYes
nameNo
noteNo
labelYes
nearbyNo
readAtYes
councilNo
currentYes
historyYes
parkingNo
heldBackNo
citationsYesEvery source the result rests on. Cite url; give checkedOn or publishedOn.
markdownUrlNo
historySinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds behavior the annotations do not: results are a current snapshot, they include notices no longer published (archived material, not just active items), and each item carries its source URL and dates — useful trust and provenance context for an agent that will cite the output.

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 payload enumeration, then input forms, then the language caveat — a sensible order with no filler sentences. The opening sentence is long and comma-chained, but every listed item is a distinct data category an agent might need to know is present.

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

Completeness5/5

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

For a single-parameter read tool with a full output schema and rich annotations, the description covers everything the agent needs: what the record contains, which input shapes are accepted, and the language preference. Return-value structure is correctly left to the output schema rather than duplicated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the mechanical constraints are already documented. The description still earns credit by giving concrete, differentiated examples of each accepted form — „бул. Цар Симеон“, „Кършияка“, „Кючука“, „Тракия, бл. 14“ — which clarifies that nicknames and block-qualified addresses are valid and that Bulgarian input works best, information the flat schema string does not convey.

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 concrete scope (one Plovdiv street or quarter) and enumerates exactly what the record aggregates: water interruptions, road works, traffic changes, municipal notices, council decisions, parking zone, nearby places, and withdrawn notices. That enumeration makes it distinguishable from a generic change feed such as plovdiv_changes or a Sofia equivalent without needing to open the schema.

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?

The description makes the trigger condition clear — you call it when you need everything known about a single named place — and it spends its closing sentences telling the agent which input shapes qualify (street, quarter, local nickname, Тракия block), which directly governs when the call will succeed. It stops short of naming a sibling to use instead for Sofia or for a cross-place change query, so no explicit exclusions or routing are given.

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