Skip to main content
Glama
Sign In

Dados Pt

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dados Pt List Organizations

dados_pt_list_organizations
Read-onlyIdempotent

List or search the organizations (Portuguese government bodies and other publishers) that publish open data on dados.gov.pt, with their dataset counts and portal pages.

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,
      "query": "Saúde",
      "page_size": 20
    },
    "name": "dados_pt_list_organizations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number (default 1).
queryNoFull-text search over organization names.
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 readOnly, idempotent, non-destructive and open-world, so the safety profile needs no restating. The description adds genuinely new context by telling the agent what each record contains — dataset counts and portal pages — which matters given there is no output schema. It does not discuss pagination limits or result ordering, but the schema's page/page_size fields cover the mechanics.

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?

A single sentence that front-loads the action and resource, with the clarifying parenthetical and the returned-attributes clause both earning their place. No filler, no restatement of the title.

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 simple, unauthenticated, read-only listing tool with three fully documented optional parameters, this is nearly complete: it establishes scope, searchability, and the shape of each returned record in the absence of an output schema. Only pagination behavior and total-count/ordering semantics are left unstated.

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%, with page, query and page_size each documented including defaults and the 1-50 range. The description adds no parameter-level 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?

Specific verb+resource: 'List or search the organizations ... that publish open data on dados.gov.pt'. The parenthetical clarifies what 'organizations' means here, and the resource noun (organizations vs. datasets) inherently separates it from dados_pt_search_datasets and dados_pt_get_dataset. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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?

'List or search' implies the two modes (call with no query to enumerate, supply a query to full-text search), and the example inputs reinforce that. There is no explicit statement of when to reach for this versus the dataset-oriented siblings, nor any exclusions or prerequisites. Usage is inferable but not spelled out.

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