Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver detalle de una institución pública

get_institucion_info
Read-only

Retrieve an Ecuadorian public institution's acronym, sector, description, and websites by ID. Use the ID from list_instituciones to fetch official gob.ec details.

Instructions

One gob.ec institution's acronym, sector, description and websites. Take institucion_id from list_instituciones (SRI=8, IESS=163, Registro Civil=23); for its procedures use search_tramites.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
institucion_idYesInstitution ID (e.g. "8")

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 / institucion_id / description
      Added value: +"Institution ID (e.g. \"8\")"
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / institucion_id / title
      Removed value: -"Institucion Id"
    • removedInput schema / title
      Removed value: -"get_institucion_infoArguments"
    • removedOutput schema / title
      Removed value: -"get_institucion_infoDictOutput"
  4. First observedv0.8.12

TDQS

A3.9/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 the safety profile is covered structurally. The description adds the returned field set but says nothing about errors, missing institutions, or auth needs, so it contributes only modest behavioral context.

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 compact clauses: the return content is front-loaded, followed by ID sourcing and the related-tool route. No filler, no repetition of the title, and 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?

For a simple read-only lookup, the definition supplies the ID source, the returned fields, and the sibling for procedures. With annotations covering safety and no output schema to explain, nothing essential is missing, though the lack of an explicit verb keeps it slightly shy of fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by supplying concrete ID mappings (SRI=8, IESS=163, Registro Civil=23) that the schema only shows as 'e.g. "8"'. This meaningfully helps the agent populate institucion_id correctly.

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 the specific resource (one gob.ec institution) and enumerates the returned fields (acronym, sector, description, websites), which makes it clearly distinct from the plural list_instituciones sibling. The retrieval verb is only implied by the noun phrase rather than stated, but an agent can still tell what the tool returns without opening the schema.

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?

It explicitly routes the agent: take institucion_id from list_instituciones, and use search_tramites for procedures. That names the source and the alternative for related data. It stops short of stating when NOT to use this tool, but the context is clear.

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