Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver un informe de datos abiertos de Contraloría

get_contraloria_informe
Read-only

Fetch rows from a Contraloría CSV of approved audit reports or annual-plan metadata and a read_pdf pointer using an informe_id from list_catalogo.

Instructions

Rows of one Contraloría audit-reports CSV (one row per approved report), or metadata and a read_pdf pointer for an annual plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsNoNumber of data rows to preview (default: 50, max: 200)
formatNotext summary (default) or json structured result.text
informe_idYesAn id from list_catalogo(fuente='contraloria')

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. Changed1 schema field changedv0.11.0
    • changedInput schema / properties / informe_id / description
      Previous value: -"An id from list_contraloria_informes"New value: +"An id from list_catalogo(fuente='contraloria')"
  3. Changed3 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / informe_id / description
      Added value: +"An id from list_contraloria_informes"
    • addedInput schema / properties / rows / description
      Added value: +"Number of data rows to preview (default: 50, max: 200)"
  4. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / informe_id / title
      Removed value: -"Informe Id"
    • removedInput schema / properties / rows / title
      Removed value: -"Rows"
    • removedInput schema / title
      Removed value: -"get_contraloria_informeArguments"
    • removedOutput schema / title
      Removed value: -"get_contraloria_informeDictOutput"
  5. First observedv0.8.12

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint). The description adds genuinely new behavioral context: the result is either row-oriented CSV data (one row per approved report) or metadata plus a read_pdf pointer for annual plans, disclosing an unusual dual-return behavior that the annotations do not convey.

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 compact sentence with no filler, front-loading the primary return type before the annual-plan exception. It is dense but earns its words; the dual-mode clause is slightly cryptic but purposeful.

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?

With no output schema, the description carries the burden of explaining returns and does so only briefly. It omits which condition triggers the metadata/read_pdf branch and how the rows preview relates to the full dataset, leaving a meaningful gap for a data-retrieval tool.

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 every parameter (informe_id, rows, format) is documented in the schema itself. The description adds no syntax, format, or constraint detail beyond what the schema already provides, so the baseline of 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?

The description names a specific resource ('one Contraloría audit-reports CSV') and states what comes back (rows, one per approved report), so the agent knows the subject matter precisely. It does not, however, differentiate itself from adjacent tools such as get_informe_igepn or get_contrato_info, and it lacks an explicit verb.

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?

There is no explicit 'use this when' guidance or exclusion against alternatives. Usage is only implied by the dual-mode framing (CSV rows vs. annual-plan metadata plus a read_pdf pointer), which hints at a follow-up chaining step but leaves the selection criteria to inference.

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