Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar división político-administrativa del Ecuador

lookup_ubicacion
Read-only

Find Ecuadorian provinces, cantons, and parroquias with INEC codes, region, and population; filter parroquias by canton or province.

Instructions

Look up Ecuador's provinces, cantons and parroquias with INEC codes, region and population. For parroquias, filter by canton and/or provincia.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nivelNoauto | provincia | canton | parroquiaauto
queryNoName or code (e.g. "Pichincha", "Cuenca", "Tumbaco", "170150")
cantonNoOptional canton filter (useful for parroquias)
formatNotext summary (default) or json structured result.text
regionNoOptional natural region for provinces/cantons
provinciaNoOptional province filter

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.10.0
    • addedInput schema / properties / canton / description
      Added value: +"Optional canton filter (useful for parroquias)"
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / nivel / description
      Added value: +"auto | provincia | canton | parroquia"
    • addedInput schema / properties / provincia / description
      Added value: +"Optional province filter"
    • addedInput schema / properties / query / description
      Added value: +"Name or code (e.g. \"Pichincha\", \"Cuenca\", \"Tumbaco\", \"170150\")"
    • addedInput schema / properties / region / description
      Added value: +"Optional natural region for provinces/cantons"
  2. Changed8 schema fields changedv0.8.14
    • removedInput schema / properties / canton / title
      Removed value: -"Canton"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / nivel / title
      Removed value: -"Nivel"
    • removedInput schema / properties / provincia / title
      Removed value: -"Provincia"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / region / title
      Removed value: -"Region"
    • removedInput schema / title
      Removed value: -"lookup_ubicacionArguments"
    • removedOutput schema / title
      Removed value: -"lookup_ubicacionDictOutput"
  3. First observedv0.8.12

TDQS

A3.5/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. The description adds the returned attributes (INEC codes, region, population) but says nothing about output volume or how the 'auto' level resolves.

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 tight sentences, front-loaded with the core purpose followed immediately by the filtering rule. No filler.

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 no explanation, and params are fully documented. Still missing context on what nivel='auto' resolves to and how the region filter behaves for provinces/cantons.

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 the baseline is 3. The description reinforces the filtering role of canton/provincia for parroquias, but adds no syntax or format detail beyond what the schema already provides.

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 ('Look up') and resource (Ecuador's provinces, cantons and parroquias) with the returned attributes (INEC codes, region, population). The resource is unique among siblings, but the description does not explicitly contrast itself with any of the many search_* tools.

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?

It tells the agent to filter parroquias by canton and/or provincia, which is useful conditional guidance. However, it gives no when-to-use vs alternatives framing and no exclusions or prerequisites, leaving usage largely implied.

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