Skip to main content
Glama
Sign In
mcp-pt

mcp-pt

by marcelogdomingues
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

open_data_search

Search the Portuguese open-data portal for datasets by keyword, such as 'população' or 'covid'. Get relevant results from dados.gov.pt in a single query.

Instructions

Search the Portuguese open-data portal dados.gov.pt for datasets by keyword (data: dados.gov.pt / uData).

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch terms, e.g. 'população', 'covid', 'ambiente'
pageSizeNoHow many datasets to return (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It discloses the tool searches a specific portal and mentions the keyword parameter, but does not detail return format, pagination, or rate limits. However, the clarity on resource and action is sufficient for a simple search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that packs significant information—resource, action, location, and keyword examples. It is front-loaded and earns its place with no filler. A slight improvement could include a brief note on return format.

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 the low complexity (2 simple parameters, no output schema or nested objects), the description is largely adequate. It covers the main search behavior and parameter usage. It lacks details on expected output structure or pagination, but for a simple keyword search, this is acceptable.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds value by giving example query terms ('população', 'covid', 'ambiente') and explaining pageSize's purpose and default, going beyond the schema's basic description. This additional guidance helps the agent craft effective queries.

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 the tool searches a specific open-data portal (dados.gov.pt) for datasets by keyword, with the key resource and action explicit. It distinguishes itself from sibling tools (e.g., fuel_prices, weather_forecast) which target different data sources and domains.

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?

The description gives a clear search context and example keywords, implying usage for dataset discovery on the Portuguese portal. It does not explicitly state when not to use it or name alternatives, but the sibling tools (e.g., fuel_prices, ine_indicator) serve distinct purposes, making the context clear.

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

Deploy Server

Other Tools