Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver detalle de un trámite gubernamental

get_tramite_info
Read-only

Retrieve an Ecuadorian government procedure's requirements, beneficiaries, cost, and responsible institution using its trámite ID from search results.

Instructions

One gob.ec trámite's requirements, beneficiaries, cost and responsible institution (tramite_id from search_tramites).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
tramite_idYesThe procedure ID (e.g. "18009")

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.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / tramite_id / description
      Added value: +"The procedure ID (e.g. \"18009\")"
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / tramite_id / title
      Removed value: -"Tramite Id"
    • removedInput schema / title
      Removed value: -"get_tramite_infoArguments"
    • removedOutput schema / title
      Removed value: -"get_tramite_infoDictOutput"
  4. First observedv0.8.12

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the payload covers requirements, beneficiaries, cost and responsible institution, which is useful, but says nothing about auth, rate limits, caching, or error behavior.

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 the resource front-loaded and no filler. It is a noun-phrase fragment rather than a full sentence, which is terse to the point of being clipped, but nothing is wasted.

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 compensates well by naming the returned fields, so an agent knows roughly what it will get. It is still light on preconditions and does not address the format parameter's effect, leaving a small gap.

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 both parameters (tramite_id and format) are already documented, which sets the baseline at 3. The description contributes one genuine extra: the provenance of tramite_id from search_tramites, but it does not touch the format option at all.

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?

Names the specific resource (a gob.ec trámite) and enumerates exactly what it returns: requirements, beneficiaries, cost, and responsible institution. The parenthetical linking to search_tramites also separates it from siblings like get_tramite_estadisticas, which covers statistics rather than detail.

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 parenthetical '(tramite_id from search_tramites)' implies the required upstream lookup, so usage is inferable, but there is no explicit statement of when to call this versus search_tramites or get_tramite_estadisticas, and no exclusions or prerequisites stated.

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