Skip to main content
Glama
Sign In
EcuDataMCP

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Verificar cumplimiento de obligaciones patronales (IESS)

get_certificado_cumplimiento_patronal
Read-only

Verify IESS contribution compliance for an employer (RUC) or individual (cédula) and return the status in text or JSON.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identificacion": "<identificacion>"
    },
    "name": "get_certificado_cumplimiento_patronal"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
sourceNo
metadatosYes
url_fuenteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "metadatos": {
+      "properties": {
+        "contrato": {
+          "const": "ecudatamcp.response.v1"
+        }
+      },
+      "required": [
+        "contrato"
+      ],
+      "type": "object"
+    },
+    "source": {},
+    "url_fuente": {}
+  },
+  "required": [
+    "metadatos"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  3. 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."
  4. 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"
  5. First observedv0.8.12

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and external-lookup behavior are covered structurally. The description's contribution beyond that is limited to defining what 'cumplimiento' means (being current on contributions); it says nothing about data freshness, whether it checks only the latest period or a history, or whether the query can fail for unknown RUC/cédula.

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 short sentences, front-loaded with the core purpose and immediately followed by the disambiguation clause. No filler, no restatement of the tool name.

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 an output schema present and full parameter documentation, the description only needs to frame the purpose and scope, which it does. The one residual gap is that 'is current' leaves the time window implicit — an agent can't tell whether this covers the latest period only or historical compliance.

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 coverage is 100% and both parameters are documented in the schema, including the enum and default for format. The description reinforces the identificacion semantics by mapping employer to RUC and person to cédula, which is useful but duplicates information the schema already carries.

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 — whether an employer (RUC) or person (cédula) is current on IESS contributions — and explicitly negates a common misinterpretation ('not a headcount'). It also names the sibling tool that covers the excluded case, so the agent can distinguish this from get_financials without opening either 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?

It gives clear routing guidance for the main ambiguity: use this for IESS compliance, use get_financials' n_empleados for employee counts. It doesn't discuss when to prefer this over other IESS-adjacent tools such as get_iess_archivos, but the exclusion it does state is the one an agent would most likely get wrong.

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