Skip to main content
Glama
Bigred97

Australian Institute of Health and Welfare

search_datasets

Fuzzy-search the curated AIHW dataset catalog to find datasets on mortality, cancer, health expenditure, and more. Returns ranked results.

Instructions

Fuzzy-search the curated AIHW dataset catalog.

All datasets ship hand-curated in v0.1: long-term mortality (GRIM), regional mortality (MORT), cancer incidence and mortality, health expenditure, youth justice detention, and the public hospitals register.

Examples: # Find a dataset that gives deaths by cause results = await search_datasets("mortality cause of death") # → [{id: 'GRIM_DEATHS', name: 'GRIM — long-term mortality', ...}]

# Discover what's available on cancer
results = await search_datasets("cancer")

Returns: List of DatasetSummary (id, name, description, update_frequency, is_curated), ranked by relevance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return, ranked by relevance.
queryYesFree-text search query. Matches against dataset IDs, names, descriptions, and curated search keywords. Case-insensitive.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description fully carries the burden. It discloses the return type and catalog contents, implying a read-only search operation. While it doesn't discuss authentication or rate limits, the provided context about fuzzy matching and ranked results adds value.

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?

The description is concise and well-structured, starting with the core purpose, followed by catalog context, usage examples, and return type. Every sentence contributes meaningfully.

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?

The description is largely complete for a simple search tool, covering purpose, examples, return format, and catalog contents. An output schema exists, so detailed return specs are not needed. Missing discussion on error handling or empty results, but overall sufficient.

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 coverage is 100%, so baseline is 3. The description's examples illustrate typical queries but add no substantial new semantics beyond the schema's parameter descriptions and examples for 'query' and 'limit'.

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 clearly states 'Fuzzy-search the curated AIHW dataset catalog' with a specific verb and resource. Examples and return type further clarify the tool's function, and it distinguishes itself from siblings like describe_dataset and get_data.

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?

The description implies usage for discovering datasets via free-text queries but lacks explicit guidance on when to use this tool versus alternatives like list_curated or top_n. No when-not-to-use or exclusion criteria are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Bigred97/aihw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server