Skip to main content
Glama

A2A Defense & Monetization Gateway

compute_procedural_deadline

Cálculo aritmético determinista de plazos procesales judiciales y administrativos (días hábiles o calendario, descontando feriados oficiales de Perú).

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": {
      "fecha_inicio": "<fecha_inicio>",
      "dias_plazo": "<dias_plazo>"
    },
    "name": "compute_procedural_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
tipo_diasNoHABILES_JUDICIALES
dias_plazoYesCantidad de días del plazo legal
fecha_inicioYesFecha inicial (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses determinism and that official Peruvian holidays are discounted, but it omits whether the start date counts as day one, where the holiday calendar comes from, and how invalid or weekend start dates are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the core purpose front-loaded and no filler. It is efficient, though the parenthetical could have been used to clarify the counting convention instead of only restating the day types.

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 pure-computation tool with no annotations and no output schema, the definition should state what is returned (a date) and the inclusion rule for the start date. It covers the holiday and day-type behavior but leaves the agent guessing about output shape and boundary conventions.

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 67%, and the description adds real meaning for the undocumented enum parameter by explaining that 'días hábiles' means judicial business days with Peruvian holidays removed. However, it says nothing about the critical convention of whether 'fecha_inicio' is included in the count, leaving the most consequential semantic gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

The description gives a specific verb and resource ('Cálculo aritmético determinista de plazos procesales judiciales y administrativos') and narrows the domain to Peru. It is unambiguous about what the tool computes, though it does not name any sibling tool it should be preferred over.

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 is only implied: the judicial/administrative and Peru scoping suggests when the tool applies, but there is no explicit when-to-use, when-not, or alternative. An agent must infer that this is the right tool for deadline arithmetic rather than, say, a general calculator.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources