Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar contribuyentes por razón social

search_sri_ruc
Read-only

Find Ecuadorian SRI taxpayers by partial company or trade name when the RUC is unknown. Search with at least 4 characters; results are capped at 100.

Instructions

Find SRI taxpayers by partial razón social or trade name (min 4 characters) when the RUC is unknown. SRI caps results at 100.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
razon_socialYesTexto a buscar (mínimo 4 caracteres), ej.
max_resultadosNoCuántos resultados con detalle completo devolver (máx 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / max_resultados / description
      Added value: +"Cuántos resultados con detalle completo devolver (máx 100)"
    • addedInput schema / properties / razon_social / description
      Added value: +"Texto a buscar (mínimo 4 caracteres), ej."
  2. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / max_resultados / title
      Removed value: -"Max Resultados"
    • removedInput schema / properties / razon_social / title
      Removed value: -"Razon Social"
    • removedInput schema / title
      Removed value: -"search_sri_rucArguments"
    • removedOutput schema / title
      Removed value: -"search_sri_rucDictOutput"
  3. First observedv0.8.12

TDQS

A4.5/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 safety is covered structurally. The description adds real behavioral context beyond that: the minimum 4-character input constraint, partial matching behavior, and the 100-result cap imposed by the SRI source.

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 tightly packed sentences with zero filler, and the core purpose plus the min-length constraint are front-loaded ahead of the cap detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 needn't be explained, and the annotations carry the safety profile. The description covers purpose, access method, input constraint, and result cap, leaving nothing an agent needs to invoke it correctly.

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 baseline is 3. The description still adds value by clarifying that matching is partial and by extending the searchable field beyond the schema's 'razon_social' to include trade name, which the schema does not mention.

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?

Specific verb (Find) plus resource (SRI taxpayers) plus access method (partial razón social or trade name), which is exactly the kind of precise articulation that distinguishes it from the sibling get_sri_ruc_info. An agent knows this is a fuzzy name search rather than a key lookup.

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?

'when the RUC is unknown' gives a clear selection rationale that implicitly routes to get_sri_ruc_info. It stops short of naming that sibling explicitly, which would make the when-to-use condition airtight.

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