Skip to main content
Glama

siconfi_relatorio

Read-onlyIdempotent

Access official SICONFI fiscal reports (RREO, RGF, DCA) for Brazilian government entities, filtering by period, annex, account and column to analyze budget execution, debt and annual accounts.

Instructions

Demonstrativos fiscais do SICONFI, declarados pelos entes, em R$: RREO (bimestral), RGF (quadrimestral) e DCA (anual).

Sem anexo, lista os anexos disponíveis; com anexo, devolve as contas em colunas. Para achar o código do ente, use siconfi_entes.

Args: relatorio: "RREO", "RGF" ou "DCA". ente: código IBGE (35 = SP, 3550308 = São Paulo, 1 = União) ou nome; nome ambíguo pede uf ou esfera. exercicio: ano (padrão: ano anterior). periodo: RREO, bimestre 1 a 6 (padrão 6); RGF, quadrimestre 1 a 3 ou semestre 1 a 2. Não vale para DCA. anexo: ex.: "01" (RREO, balanço orçamentário), "02" (RGF, dívida consolidada), "I-C" (DCA); aceita o nome. conta: trecho do nome da conta, ex.: "pessoal". coluna: trecho do nome da coluna, ex.: "empenhadas". uf: sigla, para desambiguar o ente. esfera: "U", "E", "D" ou "M". poder: só RGF: "E" (padrão), "L", "J", "M" ou "D". periodicidade: só RGF: "Q" (padrão) ou "S". simplificado: demonstrativo simplificado (municípios com menos de 50 mil habitantes). max_linhas: contas devolvidas (padrão 60).

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": {
      "relatorio": "<relatorio>",
      "ente": "<ente>"
    },
    "name": "siconfi_relatorio"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNo
enteYes
anexoNo
contaNo
poderNoE
colunaNo
esferaNo
periodoNo
exercicioNo
relatorioYes
max_linhasNo
simplificadoNo
periodicidadeNoQ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the description sensibly spends its space on behavior the annotations cannot convey: the currency (R$), the reporting frequency per report type, the fact that `periodo` does not apply to DCA, and the defaults for exercicio, periodo and max_linhas. It does not explain what happens on truncation beyond the max_linhas default, which keeps it short of a 5.

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?

The first sentence front-loads the resource and units, and the second explains the mode switch before any parameter detail. The 'Args:' block is docstring-style and slightly dense, but each line carries distinct information, with no filler sentences.

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 13-parameter, domain-heavy tool with no output schema, the definition covers modes, defaults, valid values per report and a row limit, which is enough to call it correctly. It does not describe the shape of the returned account/column table or error behavior on invalid annex codes, which would complete the picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: all 13 parameters are documented with concrete examples (ente '3550308' or '1' for União, anexo '01'/'02'/'I-C', conta 'pessoal', coluna 'empenhadas') and with valid ranges per report type. It also notes that ambiguous names require `uf` or `esfera`, which is real disambiguation logic absent from the schema.

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 states a specific verb+resource: fiscal statements (RREO, RGF, DCA) declared by government entities, in BRL, via SICONFI. It also names the sibling siconfi_entes for entity-code lookup, so the agent can separate this tool from the entity-lookup tool without opening either 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?

It clearly distinguishes the two operating modes: without `anexo` it lists available annexes, with `anexo` it returns the accounts as columns, and it points to siconfi_entes for resolving entity codes. That is strong when-to-use guidance, but it never states exclusions or prerequisites such as what to do when a report has no data for a given period.

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