Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Consultar información pública de un RUC

get_sri_ruc_info
Read-only

Fetch public SRI records for a 13-digit Ecuadorian RUC to view taxpayer name, status, type, activity, dates, and registered establishments. Excludes tax amounts.

Instructions

Public SRI record for one 13-digit RUC: name, status, type, activity, dates and registered establishments. No tax amounts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rucYesExact 13-digit Ecuadorian RUC
formatNotext summary (default) or json structured result.text
include_establecimientosNoInclude registered establishments

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.12.0
    • changedInput schema / properties / include_establecimientos / description
      Previous value: -"incluir establecimientos registrados"New value: +"Include registered establishments"
    • changedInput schema / properties / ruc / description
      Previous value: -"RUC ecuatoriano exacto de 13 dígitos"New value: +"Exact 13-digit Ecuadorian RUC"
  3. Changed3 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / include_establecimientos / description
      Added value: +"incluir establecimientos registrados"
    • addedInput schema / properties / ruc / description
      Added value: +"RUC ecuatoriano exacto de 13 dígitos"
  4. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / include_establecimientos / title
      Removed value: -"Include Establecimientos"
    • removedInput schema / properties / ruc / title
      Removed value: -"Ruc"
    • removedInput schema / title
      Removed value: -"get_sri_ruc_infoArguments"
    • removedOutput schema / title
      Removed value: -"get_sri_ruc_infoDictOutput"
  5. First observedv0.8.12

TDQS

A3.8/5.0
Behavior4/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 genuine behavioral context beyond that: it identifies the data as public SRI records and explicitly scopes out tax amounts, telling the agent what will NOT be returned.

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 with zero waste. The core resource and identifier format are front-loaded, and the scope caveat is a short, high-value clause.

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 lists the return fields, and annotations plus full schema coverage handle safety and parameters. It is close to complete, though it does not describe output shape or behavior for invalid/missing RUCs.

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 schema already documents all three parameters (ruc, format, include_establecimientos). The description echoes the 13-digit RUC constraint and the establishments field but adds no syntax or formatting detail beyond what is already structured.

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+resource (public SRI record for one 13-digit RUC) and enumerates the fields returned (name, status, type, activity, dates, establishments). The 'one 13-digit RUC' phrasing implicitly differentiates it from search_sri_ruc, but it never names that 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?

Usage is only implied: the singular 'for one 13-digit RUC' suggests a single-record lookup, and 'No tax amounts' hints at the scope boundary, but there is no explicit when-to-use statement or reference to search_sri_ruc for bulk/multi-record lookups.

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