Skip to main content
Glama

Atualizar modelos extraídos do PJe-Calc

modelos_atualizar
DestructiveIdempotent

Refaz os modelos usados pelo gerador a partir da instalação: "verbas" (com o PJe-Calc em execução: lança todas as verbas do Expresso num cálculo temporário, exporta, monta a biblioteca e exclui o temporário) ou "catalogos" (com o PJe-Calc…

Instructions

Refaz os modelos usados pelo gerador a partir da instalação: "verbas" (com o PJe-Calc em execução: lança todas as verbas do Expresso num cálculo temporário, exporta, monta a biblioteca e exclui o temporário) ou "catalogos" (com o PJe-Calc PARADO: lê municípios, assuntos CNJ e feriados do banco H2). O calculo_criar e o tabelas_atualizar já refazem a biblioteca sozinhos na primeira vez em cada PJe-Calc e depois de cada sincronização de tabelas (que muda as verbas do Expresso); use para forçar.

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": {
      "alvo": "<alvo>"
    },
    "name": "modelos_atualizar"
  }
}

Input Schema

NameRequiredDescriptionDefault
alvoYes"verbas": biblioteca das verbas do Expresso; "catalogos": municípios, feriados, pisos e demais catálogos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.16.0-mcp.14
    • addedInput schema / properties / alvo / description
      Added value: +"\"verbas\": biblioteca das verbas do Expresso; \"catalogos\": municípios, feriados, pisos e demais catálogos."
  2. First observedv2.16.0-mcp.13

TDQS

A4.5/5.0
Behavior4/5

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

With annotations declaring destructiveHint=true and idempotentHint=true, the description still adds real value: it spells out that the verbas path creates a temporary cálculo, exports it, builds the library and deletes the temporary, which explains the destructive flag and the side effects. It also discloses the required PJe-Calc state per mode. It stops short of saying what is returned or how long the rebuild takes.

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?

One dense, front-loaded sentence starting with the action, with the two modes as clearly delimited parentheticals. It is heavy with nested clauses, but nearly every clause carries decision-relevant information; only the long parenthetical about table synchronization could be tightened.

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 one-parameter mutation tool with annotations covering safety, the description supplies purpose, mode selection, preconditions and side effects — enough to call it correctly. The only gap is the absence of any statement about the result of the rebuild (success signal, errors if PJe-Calc is in the wrong state).

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 coverage is 100% with a single enum, so the baseline is met by the schema alone. The description nonetheless adds operational meaning to each enum value beyond the schema's one-liner — which mode needs PJe-Calc running, which reads municípios/assuntos CNJ/feriados from the H2 database.

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?

States a specific verb ("Refaz os modelos") and the exact resource (biblioteca de verbas do Expresso / catálogos lidos do banco H2), splitting the two modes explicitly. It also names calculo_criar and tabelas_atualizar, so an agent can distinguish this from siblings that rebuild the same library automatically.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ("use para forçar") versus when-not-to (calculo_criar and tabelas_atualizar already rebuild on first run per PJe-Calc and after each table sync). It also states the precondition that selects each mode: PJe-Calc em execução for verbas, PJe-Calc PARADO for catalogos.

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