mcp-juridico-brasil

Overview Schema Source Related Servers Discussions Admin

calcular_proximo_prazo

Calculate the next procedural deadline in business days using the Brazilian forensic calendar, accounting for recess and state/national holidays.

Instructions

Calcula o próximo prazo processual em dias úteis com calendário forense.

Implementa art. 219 (dias úteis), art. 224 (termo inicial no dia seguinte) e art. 220 CPC (suspensão no recesso forense 20/dez a 20/jan).

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": {
      "numero_processo": "<numero_processo>",
      "tribunal": "<tribunal>"
    },
    "name": "calcular_proximo_prazo"
  }
}

Input Schema

Name	Required	Description
`uf`	No	Sigla da UF para incluir feriados estaduais no cálculo (ex: 'SP', 'RJ', 'MG'). Se omitida, usa apenas feriados nacionais.
`tipo_ato`	No	Tipo do ato processual para selecionar prazo CPC (ex: 'Contestacao', 'Embargos de Declaracao'). Se omitido, usa prazo padrão de 15 dias úteis.
`tribunal`	Yes	Sigla do tribunal (ex: 'TJSP', 'TRF1').
`numero_processo`	Yes	Número no formato CNJ (NNNNNNN-DD.AAAA.J.TT.OOOO).
`data_intimacao_iso`	No	Data de intimação/publicação em ISO 8601 (ex: '2025-01-15'). Se omitida, usa a data da última movimentação disponível no DataJud.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Aug 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations present, the description carries the full behavioral burden. It discloses the key calculation behavior: business days, next-day start term, and judicial recess suspension from 20 Dec to 20 Jan. It does not describe fallback behavior or errors, but the core behavior is explicit and non-destructive.

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 with the core purpose front-loaded and the legal details compactly presented. Every phrase contributes value and there is 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?

The description is complete for a calculation tool: it states the legal rules, the calendar scope, and the calculation behavior. The input schema thoroughly documents all parameters, and an output schema exists, so return values do not need to be explained in the description.

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 baseline is 3. The description adds legal context but does not provide parameter-level semantics beyond what the schema already documents for uf, tipo_ato, tribunal, and data_intimacao_iso.

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 names a specific verb and object: 'Calcula o próximo prazo processual em dias úteis com calendário forense.' It also cites the exact CPC articles implemented, clearly distinguishing it from sibling tools such as buscar_processo_por_numero and listar_movimentacoes.

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?

The description makes the intended use obvious: calculate a procedural deadline using business days and forensic-calendar rules. It does not explicitly list exclusions or alternative tools, but none of the sibling tools appear to offer the same deadline-calculation function.

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