Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Consultar datos de un indicador del SUT

query_sut_indicador
Read-only

Query Ecuador's SUT indicator data by selecting fields, applying equality filters, and setting a row limit. Retrieve live results for analysis without credentials.

Instructions

Live query of one SUT dashboard's data model with any combination of campos, optional equality filtros (plain columns only) and a row limite.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
camposYesField labels exactly as returned by get_sut_indicador_schema.
formatNotext summary (default) or json structured result.text
limiteNoRow cap applied server-side by the query itself.
filtrosNoOptional {campo: valor} equality filters, plain columns only.
indicadorYesA key from list_sut_indicadores.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.10.0
    • addedInput schema / properties / campos / description
      Added value: +"Field labels exactly as returned by get_sut_indicador_schema."
    • addedInput schema / properties / filtros / description
      Added value: +"Optional {campo: valor} equality filters, plain columns only."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / indicador / description
      Added value: +"A key from list_sut_indicadores."
    • addedInput schema / properties / limite / description
      Added value: +"Row cap applied server-side by the query itself."
  2. Changed7 schema fields changedv0.8.14
    • removedInput schema / properties / campos / title
      Removed value: -"Campos"
    • removedInput schema / properties / filtros / title
      Removed value: -"Filtros"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / indicador / title
      Removed value: -"Indicador"
    • removedInput schema / properties / limite / title
      Removed value: -"Limite"
    • removedInput schema / title
      Removed value: -"query_sut_indicadorArguments"
    • removedOutput schema / title
      Removed value: -"query_sut_indicadorDictOutput"
  3. First observedv0.8.12

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds only that the query is 'Live' (real-time) and server-side capped, which is useful but thin; rate limits, auth needs, or result size behavior beyond the cap are not disclosed.

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?

A single dense sentence with the core operation front-loaded and zero filler. It is appropriately sized, though extremely terse for a tool with five parameters and a two-step setup.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. However, the description omits the cross-tool dependency chain (valid values for 'indicador' and 'campos' come from sibling tools), which an agent needs to invoke this correctly.

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 five parameters are already documented in the schema, including the 'plain columns only' filter constraint the description echoes. The description adds no format, syntax, or default detail beyond what the schema provides, so the baseline 3 is appropriate.

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 (a SUT dashboard's data model) and names the parameters it accepts (campos, filtros, limite). The word 'Live' and 'data model' implicitly set it apart from list_sut_indicadores and get_sut_indicador_schema, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no reference to the prerequisite workflow (list_sut_indicadores to pick 'indicador', get_sut_indicador_schema to pick 'campos'). The 'plain columns only' note is a constraint rather than usage direction, leaving the agent to infer context entirely.

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