Índices AR

Días hábiles y vencimientos

dias_habiles

Cuenta los días hábiles (lunes a viernes sin feriados nacionales) entre dos fechas, o suma N días hábiles a una fecha para calcular un vencimiento. Devuelve también los feriados que caen en el rango. Costo: 1 crédito(s).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dias_habiles"
  }
}

Input Schema

Name	Required	Description
`desde`	No	Fecha inicial, YYYY-MM-DD. Por defecto hoy.
`hasta`	No	Fecha final (inclusive) para contar días hábiles
`sumar_dias_habiles`	No	Alternativa: cuántos días hábiles sumar a `desde`

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden and discloses weekday-only counting, exclusion of national holidays, returned holidays, and a 1-credit cost. However, it omits which country's holiday calendar is used, how conflicts between hasta and sumar_dias_habiles are handled, and output details.

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: core calculation, return information, and cost are presented in three short clauses. There is no wasted wording.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple calculation tool with no annotations and no output schema, it covers the core behavior, returned holidays, and cost. It remains incomplete because the holiday calendar source and exact output shape are not specified, which an agent would need for fully correct use.

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 the schema already documents defaults, ranges, and parameter meanings. The description reinforces the two alternative modes but adds little syntax or constraint detail beyond what the schema provides, aside from an implicit 'or' relationship.

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 specific verbs and resources: it counts business days between two dates or adds N business days to a date to calculate a due date. It clearly distinguishes the two calculation modes without requiring the 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 explains the two usage modes internally: use dates for counting between dates, or use sumar_dias_habiles for a deadline calculation. It does not state exclusions or compare against sibling tools, but the intended contexts are clear.

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

All Índices AR 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?