Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Consultar los datos de un recurso (DataStore)

query_resource_data
Read-only

Query tabular CKAN resources directly through the DataStore without downloads. Filter, search, sort, and paginate Ecuadorian open government datasets by resource ID.

Instructions

Query a tabular CKAN resource through the DataStore without downloading it: full-text query, exact filters (filters_json), sort and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsNoNumber of records to return (default 20, max 100)
sortNoOptional sort expression, e.g. "anio desc"
queryNoOptional full-text search across datastore fields
formatNotext summary (default) or json structured result.text
offsetNoPagination offset (default 0)
sourceNoCKAN portal; nacional (default), cuenca, latacunga or iadb.nacional
resource_idYesResource UUID (from list_dataset_resources)
filters_jsonNoOptional JSON object of exact field filters, e.g. '{"provincia":"Pichincha"}'

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. Changed8 schema fields changedv0.10.0
    • addedInput schema / properties / filters_json / description
      Added value: +"Optional JSON object of exact field filters, e.g. '{\"provincia\":\"Pichincha\"}'"
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / offset / description
      Added value: +"Pagination offset (default 0)"
    • addedInput schema / properties / query / description
      Added value: +"Optional full-text search across datastore fields"
    • addedInput schema / properties / resource_id / description
      Added value: +"Resource UUID (from list_dataset_resources)"
    • addedInput schema / properties / rows / description
      Added value: +"Number of records to return (default 20, max 100)"
    • addedInput schema / properties / sort / description
      Added value: +"Optional sort expression, e.g. \"anio desc\""
    • addedInput schema / properties / source / description
      Added value: +"CKAN portal; nacional (default), cuenca, latacunga or iadb."
  3. Changed10 schema fields changedv0.8.14
    • removedInput schema / properties / filters_json / title
      Removed value: -"Filters Json"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / resource_id / title
      Removed value: -"Resource Id"
    • removedInput schema / properties / rows / title
      Removed value: -"Rows"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"query_resource_dataArguments"
    • removedOutput schema / title
      Removed value: -"query_resource_dataDictOutput"
  4. First observedv0.8.12

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the safety profile is covered structurally. The description adds that the operation runs through the DataStore server-side (no file download), which is useful behavioral context, but it omits rate limits, auth requirements, and result-size behavior beyond what the schema's rows/filters_json say.

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 tightly-packed sentence that front-loads the core action and scope, then lists the key capabilities. Nothing is wasted and no filler is present.

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 read-only query tool with 8 well-documented parameters, one required field, and annotations covering the safety profile, the description gives an agent enough to select and call it. The return shape is not described, but the format enum (text/json) in the schema partly mitigates that.

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 parameter meaning is already fully documented in the schema. The description names the same capabilities (full-text query, filters_json, sort, pagination) without adding syntax, format, or edge-case detail beyond the schema, 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 (Query) and resource (tabular CKAN resource through the DataStore), and the phrase 'without downloading it' implicitly carves it out from siblings like download_resource and preview_resource_data. No sibling is named explicitly, but the resource and scope are unambiguous.

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?

The phrase 'without downloading it' implies the tool is for inspecting/filtering data rather than retrieving the file, which suggests when to prefer it over download_resource. However, there is no explicit when-to-use/when-not guidance or direct routing to alternatives such as preview_resource_data or list_dataset_resources.

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