RESET Verifica

Calcular ISR de nomina

calcular_isr

ISR mensual de nomina (LISR art. 96) sobre una base gravable, para una fecha. Consume saldo (servicio NOMINA; tarifa vigente en consultar_precios). Declara la tabla y su vigencia; si la fecha cae fuera de la tabla cargada, no calcula y lo advierte. Resultado matematico, no resolucion oficial.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`base_gravable`	Yes
`fecha_calculo`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`concepto`	No
`servicio`	No
`excedente`	No
`cuota_fija`	No
`isr_causado`	No
`base_calculo`	No
`operacion_id`	No
`base_gravable`	No
`limite_inferior`	No
`porcentaje_excedente`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "fiscal_isr — 1 muestra(s), 10 campos.",
+  "properties": {
+    "base_calculo": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Base Calculo"
+    },
+    "base_gravable": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Base Gravable"
+    },
+    "concepto": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Concepto"
+    },
+    "cuota_fija": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Cuota Fija"
+    },
+    "excedente": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Excedente"
+    },
+    "isr_causado": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Isr Causado"
+    },
+    "limite_inferior": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Limite Inferior"
+    },
+    "operacion_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Operacion Id"
+    },
+    "porcentaje_excedente": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Porcentaje Excedente"
+    },
+    "servicio": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Servicio"
+    }
+  },
+  "title": "RFiscalIsr",
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes well beyond annotations by disclosing that the tool 'Consume saldo (servicio NOMINA; tarifa vigente en consultar_precios),' which is important cost behavior. It also explains date-dependent table validity and the warning behavior when the date falls outside the loaded table, plus the caveat 'Resultado matematico, no resolucion oficial.' These are meaningful non-obvious behavioral traits.

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?

The description is compact and front-loaded: it states the core operation first, then cost, validity behavior, and the official-status caveat. Every sentence contributes a distinct, non-redundant fact with no filler.

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 two-parameter calculation tool with an output schema, the description covers purpose, parameter semantics, cost, date-dependent failure behavior, and the limitation that the result is not an official resolution. Nothing critical needed to invoke the tool correctly is missing.

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 description coverage is 0%, so the description must compensate. It maps base_gravable to the taxable payroll base and links fecha_calculo to the table validity and out-of-range warning, adding real meaning beyond the schema titles. It does not explain default behavior or formats, but the schema already provides types.

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 verb and resource: 'Calcular ISR mensual de nomina (LISR art. 96) sobre una base gravable, para una fecha.' This identifies the operation, the legal basis, and the domain, making it clearly distinguishable from sibling tools like calcular_imss and calcular_laboral.

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 context is implied: it is for monthly payroll ISR calculations on a taxable base for a given date. However, it never explicitly states when to use this tool versus alternatives, nor does it name conditions or exclusions beyond the date-out-of-table behavior.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All RESET Verifica tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?