Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Verificar cumplimiento de obligaciones patronales (IESS)

get_certificado_cumplimiento_patronal
Read-only

Check whether an employer (RUC) or person (cédula) is current on IESS payroll contributions, returning compliance status rather than employee count.

Instructions

Whether an employer (RUC) or person (cédula) is current on IESS contributions. A compliance check, not a headcount; for employees use get_financials' n_empleados.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
identificacionYesA 10-digit cédula or 13-digit RUC.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / identificacion / description
      Added value: +"A 10-digit cédula or 13-digit RUC."
  2. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / identificacion / title
      Removed value: -"Identificacion"
    • removedInput schema / title
      Removed value: -"get_certificado_cumplimiento_patronalArguments"
    • removedOutput schema / title
      Removed value: -"get_certificado_cumplimiento_patronalDictOutput"
  3. First observedv0.8.12

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds that it's a compliance check (not a headcount) but does not disclose additional behavioral traits like rate limits or authentication needs. With annotations, this is adequate.

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 sentences, front-loaded with the core purpose and immediately followed by a useful disambiguation. No wasted words.

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?

For a simple read-only compliance check with an output schema and full annotation coverage, the description covers purpose, scope, and the key alternative. Nothing essential is missing.

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 parameters (identificacion and format) are fully documented in the schema. The description loosely mentions RUC/cédula but adds no syntax or format details beyond the schema. Baseline 3 is appropriate.

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 check (whether an employer or person is current on IESS contributions) and distinguishes from get_financials' headcount. Clear verb+resource and sibling differentiation.

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?

Provides context for when to use this tool (compliance check) and explicitly points to get_financials' n_empleados for employee counts. Does not mention other IESS-related siblings like list_iess_colecciones, but the primary alternative is covered.

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