Skip to main content
Glama
Sign In

Dados Pt

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dados Pt Search Datasets

dados_pt_search_datasets
Read-onlyIdempotent

Search datasets on dados.gov.pt, Portugal's national open data portal (Portuguese government open data). Returns matching datasets with title, description, publishing organization, and downloadable-resource counts.

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": {
      "page": 1,
      "sort": "-created",
      "query": "saúde pública COVID-19",
      "page_size": 20
    },
    "name": "dados_pt_search_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number (default 1).
sortNoSort order, e.g. '-created' (newest), '-reuses' (most reused).
queryNoFull-text search terms (Portuguese or English).
page_sizeNoResults per page, 1-50 (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and idempotency need no restating. The description adds value the annotations cannot: it discloses the return payload shape (title, description, publishing organization, downloadable-resource counts), which matters since there is no output schema. It omits total-result counts and pagination behavior, but that is minor here.

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?

Two sentences, zero filler: the first sentence front-loads the action, target and portal identity; the second delivers return-value content. Nothing is repeated from the schema or annotations.

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 four-parameter read-only search with no output schema, the description covers purpose, source domain, and response contents, while the schema carries all parameter detail. It stops short of explaining pagination/total-count behavior or ranking, which would complete the picture for an agent iterating over results.

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 description coverage is 100% and each of the four parameters (page, sort, query, page_size) is documented in the schema, including the '-created'/'-reuses' sort examples and the 1-50 page_size bound. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Search datasets on dados.gov.pt') and identifies the portal as Portugal's national open data portal, which an agent can map to the open-data domain immediately. It does not explicitly contrast itself with the sibling dados_pt_get_dataset, so it falls short of full sibling differentiation.

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 the discovery use case by describing search and returned matches, but never says when to search versus fetching a specific dataset via dados_pt_get_dataset, nor any exclusions or prerequisites. Usage is inferable but not stated.

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

All Dados Pt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources