Skip to main content
Glama

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

Досие на институция

institution_record
Read-onlyIdempotent

One Bulgarian public institution's record from Nishka's checked data: its contacts with the official source and the date each was checked (and when it is due again), whether its contact pages answer (weekly check), the rules and fees it handles and what changed in them since Nishka began keeping history, and letter outcomes people reported (pooled, only from 5). Facts, dates and counts — never a score or a verdict. Give the Основа id or the institution's name.

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

Input Schema

NameRequiredDescriptionDefault
cityNoplovdiv, sofia, varna or burgas; needed when the name is not an id.
institutionYesОснова id (plovdiv/service/rayon-trakia) or name, e.g. „Район Тракия“, „НАП Пловдив“, „Call Sofia“.

Output Schema

NameRequiredDescriptionDefault
recordNo
citationsYesEvery source the result rests on. Cite url; give checkedOn or publishedOn.
candidatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is low; the description nonetheless adds real behavioral context: data is 'checked' against the official source with per-item check dates and re-check dues, responsiveness is a weekly check, and reported letter outcomes are pooled and only shown from 5 reports up. The explicit 'never a score or a verdict' disclaimer usefully sets expectations for downstream reasoning. It does not say what happens if the name matches nothing or is ambiguous.

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 content is front-loaded — resource identity first, then what the record contains, then the invocation instruction. It is a single long, clause-heavy sentence, but nearly every clause conveys distinct information (provenance, cadence, pooling threshold, no-verdict policy) rather than filler.

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?

With an output schema present, the description need not explain return shapes, and annotations carry the safety profile; what remains is the epistemic framing of the data, which the description handles well (checked provenance, dates, pools of 5, no verdicts). Combined with 100% schema coverage and only two parameters, an agent has enough to call this correctly.

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%, so both parameters are already documented, and the description only echoes the id-or-name choice without adding format rules. The city parameter, which disambiguates a bare name, receives no mention in the description beyond the schema's own note. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names a specific resource — one Bulgarian public institution's record — and enumerates its contents (contacts with the official source, check dates and next-due, contact-page responsiveness, rules/fees and their changes, pooled letter outcomes). That is far more than a restatement of the name. It stops short of 5 because it never distinguishes this record from nearby siblings such as institution_responsiveness or institutions_overview.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only invocation guidance is the input instruction 'Give the Основа id or the institution's name.' There is no statement of when to reach for this tool rather than institution_responsiveness, institutions_overview, or the search tools, and no exclusions or prerequisites 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