Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver información registral de una compañía

get_compania_info
Read-only

Fetch a company's registration details from Ecuador's Supercías registry by RUC. Returns status, incorporation, representative, capital, CIIU, and address; no financials.

Instructions

Supercías registry record for one company by RUC: status, incorporation, representative, capital, CIIU, address. No financials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rucYesThe company's 13-digit RUC
formatNotext summary (default) or json structured result.text

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 / ruc / description
      Added value: +"The company's 13-digit RUC"
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / ruc / title
      Removed value: -"Ruc"
    • removedInput schema / title
      Removed value: -"get_compania_infoArguments"
    • removedOutput schema / title
      Removed value: -"get_compania_infoDictOutput"
  4. First observedv0.8.12

TDQS

A4.2/5.0
Behavior4/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 field scope and the exclusion of financials, which is genuinely useful routing context, though it says nothing about response size, latency, or failure modes for a bad RUC.

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?

A single front-loaded sentence pairing the source, the key, and the returned fields, closed by a short exclusion. No filler or redundancy.

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 usefully enumerates the returned attributes and notes the financials gap, which is what an agent needs to decide relevance. It could be slightly more complete by mentioning the text/json output choice, but the schema already carries that.

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 the 13-digit ruc and the text/json format enum are already documented in the schema. The description only restates that lookup is by RUC and adds no format or syntax detail beyond it, so the baseline 3 applies.

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?

States a specific verb+resource (registry record for one company by RUC) and enumerates the returned fields (status, incorporation, representative, capital, CIIU, address). The closing 'No financials' and the singular 'one company' implicitly separate it from get_financials and search_companias, so an agent can route 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?

'for one company by RUC' gives clear context for a single-record lookup versus a bulk search, and 'No financials' acts as an explicit exclusion steering agents to get_financials. It stops short of naming the alternative tools, so it is context rather than a full when-to-use directive.

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