Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Investigar un dataset en un solo paso

investigate_dataset
Read-only

Search Ecuadorian CKAN portals, select the top dataset, and preview its first readable resource in one step. Use individual tools if the top result is not the right match.

Instructions

One-step shortcut: search CKAN, pick the top dataset and preview its first readable resource. Use the individual tools when the top hit isn't the right one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch keywords (e.g. "empleo", "SRI recaudación")
formatNotext summary (default) or json structured result.text
sourceNoCKAN portal; nacional (default), cuenca, latacunga or iadb.nacional
preview_rowsNoData rows to preview from the chosen resource (default: 10, max: 50)

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. Changed4 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / preview_rows / description
      Added value: +"Data rows to preview from the chosen resource (default: 10, max: 50)"
    • addedInput schema / properties / query / description
      Added value: +"Search keywords (e.g. \"empleo\", \"SRI recaudación\")"
    • addedInput schema / properties / source / description
      Added value: +"CKAN portal; nacional (default), cuenca, latacunga or iadb."
  3. Changed6 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / preview_rows / title
      Removed value: -"Preview Rows"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"investigate_datasetArguments"
    • removedOutput schema / title
      Removed value: -"investigate_datasetDictOutput"
  4. First observedv0.8.12

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond that: this is a chained operation (search + select + preview) and it silently falls back to the 'first readable resource' rather than failing, which tells the agent the result may come from an indirectly chosen resource.

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 tight sentences with the primary purpose front-loaded and the fallback guidance second. No filler or restatement of the name/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 4-param, no-output-schema tool with annotations covering the safety profile, the description covers what the tool does and when to prefer it. It could say more about behavior when no dataset matches or the preview is empty, but nothing essential for correct invocation 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 all four parameters (query, format, source, preview_rows) are already fully documented in the schema, including enum values and defaults. The description adds no syntax, format, or constraint detail beyond what the schema provides, 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 chained behavior: search CKAN, take the top dataset, preview its first readable resource. This is clearly distinguishable from siblings like search_datasets and preview_resource_data, since it explicitly frames itself as the combined shortcut of those operations.

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?

Gives a clear when-to-use (one-step shortcut) and an explicit when-not-to-use condition: 'Use the individual tools when the top hit isn't the right one.' It stops short of naming which sibling tools to fall back on, so the agent must infer the alternatives from the tool list.

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