Skip to main content
Glama

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

Досие на адреса (София)

sofia_place_record
Read-onlyIdempotent

The record of one Sofia street or quarter (sprint 5): everyday places nearby with their addresses and points, and the page with the map. Sofia's official notices (water and power interruptions, road works, municipal notices) are added as each source's terms are checked; until then the record says so. Accepts a street („бул. Витоша“) or a quarter („Лозенец“). 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": "sofia_place_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesA Sofia street or quarter, in Bulgarian.

Output Schema

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

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

A3.8/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, and the description adds real behavioral context beyond them: the record is currently partial, since official notices (water/power interruptions, road works, municipal notices) are only added as each source's terms are checked, and the record itself discloses that gap. That coverage caveat is the kind of expectation-setting an agent cannot get from the annotations.

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?

Content is front-loaded: what the record is, what it contains, then the data-coverage caveat, then accepted inputs. The parenthetical '(sprint 5)' is internal jargon that earns nothing for an agent, a small deduction from an otherwise tight definition.

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?

An output schema exists, so return values need not be spelled out, and the description still previews the payload (places, addresses, points, map page). For a single-parameter read tool, the combination of scope, input shape, and the honest coverage caveat leaves nothing an agent needs missing.

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 100% and the single 'place' parameter is already documented as a Bulgarian Sofia street or quarter, so the baseline applies. The description reinforces the two acceptable granularities (street vs quarter) and the Bulgarian-language preference, but adds no format, normalization, or ambiguity-resolution detail beyond the schema.

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 precisely what comes back: a record for one Sofia street or quarter, containing nearby everyday places with addresses and points, plus a map page. The repeated 'Sofia' scoping plus the street/quarter examples clearly separate it from the Plovdiv counterpart, though the alternative is never named explicitly.

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 input-shape guidance ('Accepts a street („бул. Витоша“) or a quarter („Лозенец“)' and 'Bulgarian input works best'), which is genuinely useful for choosing the argument. It does not say when to prefer this over find_place or plovdiv_place_record, nor when a place lookup is the wrong tool, so usage is implied rather than explicit.

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