Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__nsi_bg_get_dataset

Fetch a single NSI Bulgaria dataset by numeric id as a JSON-stat 2.0 object (dimensions, categories, and the flat value array). Get ids from list_datasets. Example ids: 107 (children in kindergartens by municipality), 242 (aggregate replacement ratio).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "107"
    },
    "name": "nsi-bg__nsi_bg_get_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric dataset id, e.g. "107".
langNoLabel language. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden; it does this reasonably well by disclosing the exact response structure (JSON-stat 2.0 object, dimension/category metadata plus a flat value array) and, via 'Fetch', that this is a non-mutating read. It omits error behavior for invalid ids, response size, and whether auth or rate limits apply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler, and the essential information (what it returns, where ids come from, sample ids) is front-loaded in that order. Every clause carries information the agent needs.

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?

For a two-parameter read tool with full schema coverage, the description covers purpose, id provenance, language default via the schema, and return shape, which is sufficient to call it correctly. It does not address failure modes for unknown ids or expected payload size, which are the remaining gaps.

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 description coverage is 100%, so both parameters are already documented and the baseline is 3. The description earns above that by adding semantic meaning to the id parameter that the schema cannot: concrete id-to-content mappings (107 = kindergartens by municipality, 242 = aggregate replacement ratio) and a hint of the output contract tied to those ids.

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?

States a specific verb (Fetch), resource (a single NSI Bulgaria dataset), the key selector (numeric id), and the exact return type (JSON-stat 2.0 with dimensions, categories and flat value array). This makes it immediately distinguishable from the sibling list_datasets, which by name alone is a listing operation.

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?

Explicitly routes the agent to list_datasets as the source of valid ids and gives two concrete example ids with their meaning, so an agent knows the precondition for calling. It stops short of saying when not to use it (e.g. bulk retrieval of many datasets), so it does not reach a 5.

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.