Skip to main content
Glama
statistik-austria-mcp

statistik-austria-mcp

search_dataset

Search Austria's OGD catalog by German keyword to locate datasets and retrieve their IDs for fetching data; empty queries return recently updated datasets.

Instructions

Search the OGD catalog by keyword. By default every query word of 3+ characters must appear in a result; word parts match too. An empty query returns recently updated datasets. Titles are in German, so search with German keywords (e.g. "Bevölkerung", not "population"). Pass a result's "id" to fetch_dataset_json or fetch_dataset_csv. Some datasets aren't standard CSV tables; fetch_dataset_csv then explains why it can't load them. Pages: at most limit results (max 50); if "truncated", continue at offset + returned. Setting match_all=False returns datasets containing any query word, best matches first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo
match_allNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • addedInput schema / properties / match_all
      Added value: +{
      +  "default": true,
      +  "title": "Match All",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "title": "Offset",
      +  "type": "integer"
      +}
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, it discloses match semantics (3+ character words, word parts, match_all default/false), empty-query behavior, page truncation, and downstream CSV limitations. This is substantial behavioral context.

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?

Dense and front-loaded; every sentence adds search semantics, pagination, language guidance, or sibling-routing context. There is no filler.

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?

Given no annotations or output schema and 0% schema coverage, it covers invocation and continuation well, including result id and truncated. It still omits the full result shape and precise offset defaults.

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

Parameters5/5

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

Schema coverage is 0%, but the description gives meaning for all four parameters: query matching, limit max 50, offset continuation, and match_all false behavior. It compensates strongly for the absent schema descriptions.

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 ('Search the OGD catalog by keyword') and clearly distinguishes the tool from fetch_dataset_json/csv by routing result ids to them.

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?

Explains empty-query behavior, German keyword requirement, pagination continuation, and points to fetch tools for retrieval. It lacks an explicit 'when not to use this' statement, so it is strong 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.