portugal-mcp

sns_search_datasets

Search ~150 SNS Transparency portal datasets using Portuguese keywords to locate health data not covered by curated tools, returning dataset IDs and field names for querying.

Instructions

Search the ~150 datasets of the SNS Transparency portal (titles and descriptions are in Portuguese).

Use when the curated tools don't cover the question — e.g. hospital bed occupancy ("ocupação"), births/caesareans ("partos"), INEM pre-hospital calls, SNS 24 calls, family doctor coverage ("médico de família", "inscritos"), medicines spending, staff ("trabalhadores"), cancer screening ("rastreios"). Then call sns_query_dataset with the dataset_id and the field names returned here. Portuguese keywords work best; matching is accent-insensitive.

Args: query: Keywords, e.g. "ocupação internamento", "partos", "urgência". Empty = list all (id + title). limit: Max results (default 10, max 50; ignored when listing all).

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 2, 2026

TDQS

A4.8/5.0

Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden and does well: it discloses Portuguese-language titles/descriptions, accent-insensitive matching, empty-query listing behavior, and that limit is ignored when listing all. It does not cover error behavior or rate limits, but the key search semantics are clear.

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?

Front-loaded with the core purpose, followed by usage guidance, workflow, and parameter notes. The examples and formatting earn their place by making search behavior and follow-up steps immediately actionable.

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

Completeness5/5

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

Given an output schema exists, the description need not explain return values in detail, and it still explains the important listing behavior. It also connects the tool to sns_query_dataset, making the overall workflow complete for an agent.

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 description coverage is 0%, but the description fully compensates by explaining query as Portuguese keywords with examples, empty query as list-all returning id and title, and limit as default 10, max 50, ignored when listing all. This adds substantial meaning beyond the bare schema.

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 ~150 datasets of the SNS Transparency portal. It also distinguishes itself from curated tools and names the follow-up sibling sns_query_dataset, so an agent can place it precisely.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it: when curated tools do not cover the question, with concrete examples such as hospital bed occupancy, births, INEM calls, and cancer screening. It also states the next step: call sns_query_dataset with the returned dataset_id and field names.

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