Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver campos de un indicador del SUT o la Judicatura

get_sut_indicador_schema
Read-only

Retrieves the queryable fields, measures, and date levels for a SUT or Judicatura dashboard indicator so you can build valid queries for query_sut_indicador.

Instructions

Queryable fields of one SUT or Judicatura dashboard (fuente): columns, measures ([medida]/[suma]/[promedio]) and date levels, for query_sut_indicador.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
fuenteNosut (default) | judicaturasut
indicadorYesA key from list_catalogo(fuente=<fuente>).

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. Changed2 schema fields changedv0.12.0
    • addedInput schema / properties / fuente
      Added value: +{
+  "default": "sut",
+  "description": "sut (default) | judicatura",
+  "enum": [
+    "sut",
+    "judicatura"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / indicador / description
      Previous value: -"A key from list_catalogo(fuente='sut')."New value: +"A key from list_catalogo(fuente=<fuente>)."
  3. Changed1 schema field changedv0.11.0
    • changedInput schema / properties / indicador / description
      Previous value: -"A key from list_sut_indicadores."New value: +"A key from list_catalogo(fuente='sut')."
  4. Changed2 schema fields changedv0.10.0
    • 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."
  5. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / indicador / title
      Removed value: -"Indicador"
    • removedInput schema / title
      Removed value: -"get_sut_indicador_schemaArguments"
    • removedOutput schema / title
      Removed value: -"get_sut_indicador_schemaDictOutput"
  6. First observedv0.8.12

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds real value beyond annotations by disclosing the shape of the result — columns, measures with the [medida]/[suma]/[promedio] syntax, and date levels — which matters because there is no output schema.

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 front-loaded sentence with no filler; the return-content detail is packed into parentheticals. Slightly dense but 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 correctly fills the gap by describing the returned field categories and the measure syntax. Annotations cover safety and the schema covers all parameters, so nothing essential 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%, and the three parameters (format, fuente, indicador) are fully documented in the schema. The description merely echoes '(fuente)' and adds no syntax or constraint beyond what the schema already provides, 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 resource (queryable fields of a SUT/Judicatura dashboard) and enumerates what those fields are: columns, measures, and date levels. It also hints at its relationship to query_sut_indicador and list_catalogo, so an agent can place it, though the verb is implicit rather than explicit.

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 'for query_sut_indicador' implies this is a prerequisite/discovery step for that sibling, which is useful context. However, it never states when to call it versus alternatives (e.g. list_catalogo) or any condition, so usage is implied rather than guided.

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