Skip to main content
Glama
lucianumm

PJe-Calc MCP

by lucianumm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Extrato do FGTS -> depósitos (fgts.operacoes)

extrato_para_fgts
Read-onlyIdempotent

Process FGTS analytical statement entries and final balance to produce fgts.operacoes, deposits by competency, and checks for balance reconciliation and missing deposits.

Instructions

Recebe os lançamentos do extrato analítico do FGTS ({ competencia, data, valor, tipo: DEPOSITO|JAM|SAQUE|MULTA }) e o saldo final; devolve fgts.operacoes (depósitos e saques a deduzir), os depósitos por competência e as conferências: soma dos lançamentos = saldo; competências do período sem depósito.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
saldoNoSaldo final do extrato, para conferir a soma dos lançamentos.
periodoNoPeríodo do contrato (aaaa-mm), para acusar competências sem depósito.
documentoNoId do extrato em contrato.documentos (vira a origem das operações).
lancamentosYesLançamentos do extrato analítico: { competencia, data, valor, tipo DEPOSITO|JAM|SAQUE|MULTA }.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.16.0-mcp.14
    • addedInput schema / properties / lancamentos / description
      Added value: +"Lançamentos do extrato analítico: { competencia, data, valor, tipo DEPOSITO|JAM|SAQUE|MULTA }."
    • addedInput schema / properties / periodo / description
      Added value: +"Período do contrato (aaaa-mm), para acusar competências sem depósito."
    • addedInput schema / properties / saldo / description
      Added value: +"Saldo final do extrato, para conferir a soma dos lançamentos."
  2. First observedv2.16.0-mcp.13

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds real behavioral context beyond that: it computes and returns fgts.operacoes, per-competência deposits, and two reconciliation checks (sum = balance; competências without deposits).

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, front-loaded with the input contract then the outputs and checks. Every clause earns its place, though the inline tuple notation makes it slightly harder to parse than separated sentences.

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?

There is no output schema, so the description must carry the return-value burden, and it does: it names the produced entities and the two conferências. Nothing critical for correct invocation appears missing.

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 100%, so the schema already documents all four parameters. The description echoes the lancamentos shape ({competencia, data, valor, tipo}) but adds no syntax or format detail beyond the schema, so 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?

States a specific transform: it receives FGTS analytic-statement entries plus final balance and returns fgts.operacoes, deposits per competência, and reconciliations. The verb/resource pair (extrato -> operações) is unambiguous and no sibling overlaps it.

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 implied by the naming of input sources and output targets, but the description never states when to use this versus alternatives or what prerequisites exist. With many sibling tools present, an explicit 'use this to convert an FGTS statement extract' cue would help.

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