Skip to main content
Glama
lucianumm

PJe-Calc MCP

by lucianumm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Liquidar cálculo (teste ou a pedido do usuário)

calculo_liquidar
Idempotent

Liquidate a PJe-Calc calculation to get summary totals—gross, net, defendant-owed, and per-entry amounts—for checking or auditing labor calc results.

Instructions

Liquida o cálculo no PJe-Calc (Operações > Liquidar) e devolve os totais do Resumo do Cálculo (bruto, líquido, total devido pelo reclamado, valores por verba). Normalmente quem liquida é o usuário; use para conferir o resultado ou quando ele pedir.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regerarNoRegera as ocorrências (mantendo alterações manuais) antes de liquidar. Use depois de tabelas_atualizar; é automático quando a própria chamada atualiza as tabelas.
regionalNoTRT do processo, usado se for preciso atualizar as tabelas.
id_calculoYesNúmero do cálculo no PJe-Calc.
data_liquidacaoNodd/mm/aaaa ou aaaa-mm-dd (padrão: a sugerida pelo PJe-Calc).
ignorar_tabelasNoLiquida mesmo com tabelas desatualizadas (não recomendado).
acumular_indicesNoDesde quando acumular os índices de correção: mês subsequente ao vencimento, mês do vencimento ou a combinação dos dois (padrão: o da tela).
atualizar_tabelasNoAtualiza as tabelas de índices (online, pelo TRT informado) se não cobrirem a data de liquidação.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.16.0-mcp.14
    • addedInput schema / properties / acumular_indices / description
      Added value: +"Desde quando acumular os índices de correção: mês subsequente ao vencimento, mês do vencimento ou a combinação dos dois (padrão: o da tela)."
    • addedInput schema / properties / id_calculo / description
      Added value: +"Número do cálculo no PJe-Calc."
  2. First observedv2.16.0-mcp.13

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false for this mutation. The description adds useful context beyond them: the operation is normally user-driven, and it discloses what the call returns (bruto, líquido, total devido pelo reclamado, valores por verba), which matters since no output schema exists.

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?

Two sentences, front-loaded with the action and the returned data, with the usage caveat second. No filler, though the usage caveat could be tightened into a cleaner when/when-not clause.

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?

For a side-effecting tool with no output schema, the description compensates by naming the returned totals, and the rich schema covers all parameters including the table-refresh and regeneration flags. What is missing is any note on whether tables must be current (only implied via ignorar_tabelas) and how errors surface.

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 all seven parameters (regerar, regional, data_liquidacao, ignorar_tabelas, acumular_indices, atualizar_tabelas, id_calculo) are already documented in the schema, including the enum semantics and defaults. The description does not add parameter-level meaning beyond that, so the baseline 3 applies.

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?

Specific verb+resource ("Liquida o cálculo no PJe-Calc"), names the exact UI path (Operações > Liquidar), and states the return payload (Resumo do Cálculo totals). An agent can distinguish it from siblings like calculo_relatorio or calculo_regerar_ocorrencias without opening 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?

"Normalmente quem liquida é o usuário; use para conferir o resultado ou quando ele pedir" gives an explicit triggering condition and implicitly warns against routine use. It states when to call but does not name alternative sibling tools for adjacent needs.

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