Skip to main content
Glama

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

Търсене в Основа

search_osnova
Read-onlyIdempotent

Search Основа, checked facts about Bulgarian public services (institutions, offices, contacts, procedures, fees, where to report a problem), for Plovdiv, Sofia, Varna and Burgas. Query in Bulgarian works best. Every fact has its official source and the date it was checked; cite them.

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

Input Schema

NameRequiredDescriptionDefault
cityNoLimit to one city.
kindNoservice: an institution or office; rule: a procedure.
limitNo
queryYesWhat to look for, e.g. „лична карта“, „дупка на пътя“, „ВиК авария“.

Output Schema

NameRequiredDescriptionDefault
entriesYes
citationsYesEvery source the result rests on. Cite url; give checkedOn or publishedOn.
attributionYes

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. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds genuinely non-structured context: every fact carries an official source and a check date, and callers are expected to cite them — that shapes how results should be treated. It does not mention result volume or pagination behavior, but an output schema exists to cover return shape.

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?

Two sentences with no filler: the first establishes domain and geographic scope, the second establishes the citation contract. Front-loaded and easy to scan. Slightly dense with parenthetical enumeration, but every element carries information.

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 four parameters at 75% coverage, rich annotations, and an output schema, the description covers the essentials: what is searched, which cities, the language preference, and the obligation to cite sources. The remaining gap is routing guidance against the sibling search tools, which matters given several similarly named search endpoints.

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 75% and both enums (city, kind) are documented in the schema, so the baseline applies. The description adds real value for the required query parameter by advising Bulgarian-language queries, and the city list reiterates the enum. The limit parameter gets no mention, and the Bulgarian query examples live in the schema rather than the description.

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?

States a specific verb (search) plus a clearly scoped resource: verified facts about Bulgarian public services (institutions, offices, contacts, procedures, fees, reporting problems) limited to four named cities. The parenthetical enumeration of content types lets an agent predict what kinds of queries will return results. It does not name a sibling such as search_izvor or get_osnova_entry, so differentiation is inferred rather than stated.

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?

"Query in Bulgarian works best" and "cite them" give useful operational context for how to use results, and the domain framing implies this is the tool for factual lookups about services. However, there is no explicit statement of when to prefer this over search_izvor or get_osnova_entry, nor any exclusion or prerequisite guidance.

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