Skip to main content
Glama

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

Отговарят ли институциите

institution_responsiveness
Read-onlyIdempotent

How often institutions answered letters people sent with Nishka's help, as counts (answered, partly, no answer) per institution and kind of letter — shown only where there are at least 5 reported outcomes. Counts only: no names, no text. Institution keys look like plovdiv/water, plovdiv/power, plovdiv/municipality.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "institution_responsiveness"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoYYYY-MM-DD; default one year ago.
institutionNoAn institution key, e.g. plovdiv/water; all when omitted.

Output Schema

NameRequiredDescriptionDefault
noteNo
sinceNo
citationsYesEvery source the result rests on. Cite url; give checkedOn or publishedOn.
thresholdYes
institutionsYes

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.2/5.0
Behavior5/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 behavior the annotations cannot convey: results are counts only, contain no names or text, and are suppressed where fewer than 5 outcomes were reported. That suppression rule is exactly the kind of non-obvious behavior an agent needs to interpret sparse or missing rows.

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 leads with the core purpose, then the privacy and threshold constraints, then key format — good front-loading in two dense sentences. The trailing institution-key examples are slightly redundant with the schema's parameter description, a minor waste.

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 only two optional parameters, full schema coverage, and an output schema covering return values, the description supplies everything else an agent needs: aggregation unit, privacy constraint, minimum-sample suppression, and key syntax. Nothing required to call or interpret it correctly is 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 description coverage is 100%, so both parameters are already documented, and the description's institution-key examples (plovdiv/water, plovdiv/power) merely restate the schema's own example. The 'since' parameter and its default are not mentioned at all, so no meaning is added beyond the schema; baseline 3 applies.

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?

The description names a precise resource — aggregated counts of whether institutions answered letters sent with Nishka's help, broken down by institution and letter kind. That is a distinct data product no sibling (search_izvor, prepare_letter, plovdiv_changes) provides, so an agent can route to it without opening 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 Guidelines3/5

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

Usage is only implied: the description makes clear this is the tool for responsiveness statistics, but it never states when to prefer it over a sibling, when not to use it, or what prerequisites (e.g., a known institution key) exist. An agent must infer the call context.

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