Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__nsi_bg_list_datasets

List NSI Bulgaria open-data datasets with their numeric id and English (or Bulgarian) name. Each dataset id can be passed to get_dataset for the actual figures. Use the optional filter to substring-match dataset names (case-insensitive), e.g. 'population', 'export', 'inflation'.

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": {
      "filter": "population"
    },
    "name": "nsi-bg__nsi_bg_list_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of dataset names. Default en.
filterNoCase-insensitive substring to match against dataset names.

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?

With no annotations provided, the description carries the full burden and does disclose the meaningful traits: the response contains ids paired with names, and naming language is controlled by `lang`. It does not say how many datasets are returned, whether results are paginated, or whether the list is complete, which are the remaining behavioral gaps.

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, front-loaded with the purpose, then the downstream handoff, then parameter guidance. No filler, no repetition of the tool name, and each sentence adds a distinct piece of 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?

For a two-parameter, zero-required discovery tool with no output schema, the description covers what it returns, how filtering works, and what to do next. The only omissions are result-set size and pagination behavior, which are minor for a dataset catalog but would be useful if the catalog is large.

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 defines `lang` and `filter`, making 3 the baseline. The description earns above that by restating filter semantics ('case-insensitive substring') and supplying worked example values ('population', 'export', 'inflation') that clarify what kind of strings actually match dataset names.

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 and resource ('List NSI Bulgaria open-data datasets') and names the returned fields (numeric id and English/Bulgarian name). It also explicitly separates itself from nsi_bg_get_dataset, so an agent can distinguish discovery from retrieval without opening either schema.

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?

Gives clear context: use this to find a dataset id, then pass it to get_dataset for the actual figures, plus concrete filter examples like 'population' and 'inflation'. It stops short of stating when NOT to use it (e.g., if the id is already known, skip straight to get_dataset), so it is clear but not fully exhaustive.

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.