Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver metadata de un recurso (archivo)

get_resource_info
Read-only

Retrieve metadata for a CKAN resource: format, size, MIME type, download URL, and parent dataset by resource_id. Use it to inspect file details before previewing or querying contents.

Instructions

Metadata for one CKAN resource (file): format, size, MIME type, download URL and parent dataset. Take resource_id from list_dataset_resources; then preview_resource_data or query_resource_data for its contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
sourceNoCKAN portal; nacional (default), cuenca, latacunga or iadb.nacional
resource_idYesThe resource UUID

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 / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / resource_id / description
      Added value: +"The resource UUID"
    • 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 / format / title
      Removed value: -"Format"
    • removedInput schema / properties / resource_id / title
      Removed value: -"Resource Id"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"get_resource_infoArguments"
    • removedOutput schema / title
      Removed value: -"get_resource_infoDictOutput"
  4. First observedv0.8.12

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds the returned metadata fields, but says nothing about portal/source behavior, availability, or any per-portal caveats despite openWorldHint implying external calls. Adequate but not rich beyond the annotations.

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 short sentences with no filler; the payload description comes first and the routing/next-step guidance follows. 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 usefully enumerates the returned metadata fields, which is the right compensation, and it names the downstream tools for content retrieval. It stops short of covering multi-portal behavior or any error/not-found case, but nothing critical for calling the tool correctly is missing.

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 format, source and resource_id are already documented with enums and defaults; the baseline is 3. The description adds provenance for resource_id (comes from list_dataset_resources) but does not explain the meaning of the source portal switch or the text/json format choice beyond the schema text.

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 and resource ('Metadata for one CKAN resource (file)') and enumerates the exact fields returned: format, size, MIME type, download URL and parent dataset. It also separates itself from the content-oriented siblings (preview_resource_data / query_resource_data), so an agent can pick it without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent where resource_id comes from (list_dataset_resources) and names the alternatives to use when the contents rather than the metadata are wanted. This is a full when-to-use plus when-not-to-use routing statement.

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