Skip to main content
Glama

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

Търсене по име

find_place
Read-onlyIdempotent

Where a named place is — a park, school, hospital, institution, shop, street or quarter in Plovdiv or Sofia: from Nishka's own data first (official and curated lists, Основа, OpenStreetMap), then the map service. Returns each match with its kind, address or district, its point and the source; several matches when the name is shared (ask the person which one). Latin or Cyrillic spellings both work (Ribnitsa = Рибница).

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

Input Schema

NameRequiredDescriptionDefault
cityNoplovdiv (default) or sofia.
nameYesThe place's name, e.g. „парк Рибница“, „УМБАЛ Свети Георги“, „Mall Plovdiv“.

Output Schema

NameRequiredDescriptionDefault
stepNo
matchNo
placesYes
citationsYesEvery source the result rests on. Cite url; give checkedOn or publishedOn.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description discloses the lookup order (Nishka data first, then the map service), return fields, behavior for shared names, and Latin/Cyrillic spelling tolerance. This is rich behavioral context that materially helps invocation.

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?

The definition is front-loaded with the core purpose and remains compact despite including source order, return behavior, and transliteration details. It is slightly dense but every clause adds practical information.

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 two-parameter lookup tool with full schema coverage and an output schema, the description supplies everything an agent needs: scope, city context, source order, return shape, ambiguity handling, and spelling tolerance. No important behavioral gap remains.

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 schema already documents the name and city parameters. The description adds useful semantic detail by stating that both Latin and Cyrillic spellings work, which goes beyond the schema's examples.

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 action and resource: locating where a named place is, with examples of place types and the two supported cities. It is clear, but it does not explicitly differentiate itself from sibling tools such as the city-specific place-record tools.

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 gives clear usage context: look up a named place in Plovdiv or Sofia when its location is needed. It also tells the agent to ask the user which match to choose when a name is shared, but it does not name exclusions or alternative tools for other place-related needs.

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