Skip to main content
Glama

nbb_search

Read-onlyIdempotent

Fuzzy search the local catalogue of NBB dataflows without an API call, filtering by category and agency to return ranked hits with dimensions, frequencies, time coverage and example queries.

Instructions

Fuzzy search across the local catalogue of NBB dataflows (no API call). Filters by category and agency. Returns ranked hits with dimensions, available frequencies, time coverage and example queries.

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": "nbb_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
agencyNoall
categoryNoall
languageNoen
include_non_finalNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful trait beyond them: the search runs locally against a cached catalogue with no API call, so it is cheap and side-effect free. It says nothing about fuzzy-matching behavior or ranking mechanics, which keeps it below the top of the scale.

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 core action and scope, with no wasted words. The filtering and return content follow in a logical order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Purpose and return shape are adequately covered, and an output schema exists so return values need not be explained. However, for a six-parameter tool with zero schema coverage, leaving half the parameters undefined is a meaningful gap an agent could stumble on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description must carry parameter meaning and largely does not. It covers query, category and agency at a high level but never explains limit, language, include_non_final, or what the "all" defaults mean.

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 verb and resource ("fuzzy search across the local catalogue of NBB dataflows") and states scope ("no API call") plus filtering dimensions. It is clearly distinguishable from nbb_query or nbb_describe, though it never names a sibling explicitly.

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: an agent can infer this is the discovery step before querying, since it searches a catalogue rather than returning data. There is no explicit statement of when to prefer this over nbb_quick, nbb_query or nbb_describe, and no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.