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

Verify whether an employer (RUC) or person (cédula) is current on IESS contributions. This checks Ecuador payroll compliance, not employee headcount.

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.

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 / identificacion / description
      Added value: +"A 10-digit cédula or 13-digit RUC."
  3. 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"
  4. First observedv0.8.12

TDQS

A4.2/5.0
Behavior3/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 the semantic clarification that this is a boolean-style compliance status rather than a data listing, but says nothing about auth requirements, rate limits, or freshness of the compliance data.

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, zero filler, with the core scope stated first and the disambiguation second. Every clause earns its place.

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 correctly carries the return-value burden by stating it answers 'whether ... is current on IESS contributions.' It is complete for a single-lookup compliance check, though it could note what a non-compliant or unknown identification returns.

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%, with both params (identificacion, format) fully documented in the schema including the enum. The description reinforces identificacion's dual identity semantics (RUC for employers, cédula for persons) but adds no format or validation detail 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific check (IESS contribution compliance) over a specific resource (RUC or cédula), and explicitly differentiates itself from the sibling tool get_financials by calling out that it is 'a compliance check, not a headcount.' An agent can distinguish it from the many search_*/get_* siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the condition that selects this tool (verifying contribution compliance) and explicitly routes the agent elsewhere for the adjacent need ('for employees use get_financials' n_empleados'). This is a clear when-to-use plus a named alternative for the most likely confusion.

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