Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar compañías en el registro de Supercías

search_companias
Read-only

Search Ecuador's Supercías company registry by name or RUC to retrieve legal status, incorporation, representative, capital, CIIU, and address details.

Instructions

Search Supercías' registry of 226k+ companies by name or RUC: legal status, incorporation, representative, capital, CIIU, address. The first call may ask you to retry in 1-2 min while the export downloads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 20, max 100)
queryNoFree text matched against company name or RUC (accent-insensitive)
formatNotext summary (default) or json structured result.text
offsetNoPagination offset over the matched set
provinciaNoOptional province filter, e.g. "PICHINCHA" (substring match)
situacion_legalNoOptional legal status filter, e.g. "ACTIVA", "DISOLUCIÓN"

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. Changed6 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / limit / description
      Added value: +"Max results (default 20, max 100)"
    • addedInput schema / properties / offset / description
      Added value: +"Pagination offset over the matched set"
    • addedInput schema / properties / provincia / description
      Added value: +"Optional province filter, e.g. \"PICHINCHA\" (substring match)"
    • addedInput schema / properties / query / description
      Added value: +"Free text matched against company name or RUC (accent-insensitive)"
    • addedInput schema / properties / situacion_legal / description
      Added value: +"Optional legal status filter, e.g. \"ACTIVA\", \"DISOLUCIÓN\""
  3. Changed8 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / provincia / title
      Removed value: -"Provincia"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / situacion_legal / title
      Removed value: -"Situacion Legal"
    • removedInput schema / title
      Removed value: -"search_companiasArguments"
    • removedOutput schema / title
      Removed value: -"search_companiasDictOutput"
  4. 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, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: the first call may ask the agent to retry in 1-2 minutes while the export downloads. That is exactly the kind of trait the schema cannot express.

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?

Two sentences, front-loaded with purpose then the operational caveat, with no filler. Efficient and appropriately sized for the tool's complexity.

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?

Covers purpose, matchable keys, returned fields, and the first-call latency behavior, with annotations supplying the safety profile and the schema covering all parameters; no output schema means the field list in the description does useful work. Slightly short on pagination/filter interaction, but otherwise complete.

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 limit, query, format, offset, provincia and situacion_legal are already fully documented. The description only restates the name/RUC matching and legal-status filter (situacion_legal) without adding syntax, format or value details beyond the schema, 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 verb (Search) plus the exact resource (Supercías' registry of 226k+ companies) and enumerates the returned fields (legal status, incorporation, representative, capital, CIIU, address). It clearly marks this as a broad lookup, implicitly distinguishable from the detail-oriented sibling get_compania_info, though it never names a sibling explicitly.

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?

"Search ... by name or RUC" implies the intended usage context, and the retry note hints at first-call behavior. However, it never states when NOT to use this tool or routes the agent to get_compania_info for detail lookups, so guidance remains implied rather than explicit.

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