Skip to main content
Glama

List a Curitiba open dataset's files

dataset_files
Read-onlyIdempotent

List downloadable files for a Curitiba open-data dataset with format, size, last update, download link, and data-dictionary link—without fetching the files.

Instructions

List the downloadable files of one Portal de Dados Abertos de Curitiba dataset: name, format, size, last update, link and data-dictionary link. Returns the links without fetching them. Read-only.

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": {
      "dataset_id": "<dataset_id>"
    },
    "name": "dataset_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of the file list (50 files per page, newest first).
dataset_idYesDataset id (GUID) from open_datasets_search.

Output Schema

NameRequiredDescriptionDefault
dataYes
fetched_atYes
source_urlYes
license_noteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, non-destructive and openWorld, so 'Read-only' is redundant. The genuinely additive line is 'Returns the links without fetching them', which tells the agent no file content is downloaded — real behavioral context beyond the annotations, though nothing is said about rate limits or error behavior.

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?

Two tight sentences with the scope and return contents front-loaded, no filler. The trailing 'Read-only.' is a minor redundancy given readOnlyHint=true, which keeps it just short of a 5.

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?

An output schema exists, so the listed return fields are a helpful convenience rather than a necessity, and pagination is fully specified in the schema. The main residual gap is that the description doesn't state where the required dataset_id comes from, leaving that to the schema text.

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%, so both dataset_id (GUID pattern, sourced from open_datasets_search) and page (50 per page, newest first) are fully documented in the schema. The description adds nothing about either parameter, so the baseline 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 ('List') and resource ('downloadable files of one Portal de Dados Abertos de Curitiba dataset') and enumerates the returned fields (name, format, size, last update, link, data-dictionary link). It scopes to 'one dataset', which separates it from the sibling search tool, but never names open_datasets_search explicitly.

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?

Usage is only implied: the tool is for inspecting the files of a single already-identified dataset, and the schema (not the description) points at open_datasets_search as the source of the id. There is no explicit 'use this when / use search instead' routing and no prerequisite statement in the description itself.

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