Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver metadata de un dataset

get_dataset_info
Read-only

Retrieve metadata for one CKAN dataset—description, organization, tags, dates, license, update frequency, and publisher source URL—by dataset ID.

Instructions

Metadata for one CKAN dataset: description, organization, tags, dates, license, update frequency and the publisher's source URL. Take dataset_id from search_datasets; next list_dataset_resources for its files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
sourceNoCKAN portal; nacional (default), cuenca, latacunga or iadb.nacional
dataset_idYesThe dataset ID or slug (e.g. "registro-estadistico-de-recursos-y-actividades-de-salud-2019")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Changed3 schema fields changedv0.10.0
    • addedInput schema / properties / dataset_id / description
      Added value: +"The dataset ID or slug (e.g. \"registro-estadistico-de-recursos-y-actividades-de-salud-2019\")"
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / source / description
      Added value: +"CKAN portal; nacional (default), cuenca, latacunga or iadb."
  3. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / dataset_id / title
      Removed value: -"Dataset Id"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"get_dataset_infoArguments"
    • removedOutput schema / title
      Removed value: -"get_dataset_infoDictOutput"
  4. First observedv0.8.12

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the safety profile is covered. The description usefully enumerates the returned metadata fields, which substitutes for the missing output schema, but says nothing about sourcing behavior per portal, errors, or rate limits.

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 dense sentences with zero filler; the payload (returned fields) is front-loaded and the navigation hints follow. Every clause earns its place.

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?

With no output schema, the description carries the return-value burden and does so by listing the metadata fields returned. Portal selection (source) and output format are handled by the well-documented schema, leaving little an agent still needs; only error/edge behavior is unaddressed.

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%: dataset_id, format and source are all documented in the schema, including enum values and defaults. The description only adds the advice on where dataset_id comes from, which is marginal beyond the structured fields, so the baseline 3 applies.

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+resource (metadata for one CKAN dataset) and enumerates the returned fields, so the agent knows exactly what it gets. It also names the adjacent siblings (search_datasets upstream, list_dataset_resources downstream), distinguishing it from the search and resource-listing tools.

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?

Explicitly tells the agent where dataset_id comes from (search_datasets) and what to call next for files (list_dataset_resources), which is strong workflow routing. It does not state when to avoid this tool (e.g., when only a resource-level lookup is needed via get_resource_info), so it stops short of a 5.

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