Skip to main content
Glama

siconfi_entes

Read-onlyIdempotent

Find SICONFI entity codes for União, states, DF, or municipalities by name or IBGE code, with UF and sphere filters; returned codes are used by siconfi_relatorio.

Instructions

Procura o código de um ente (União, estado, DF ou município) no SICONFI. O código IBGE é o que siconfi_relatorio usa.

Args: busca: parte do nome ("campinas") ou código IBGE. Vazio = lista pelos filtros. uf: sigla da UF, para restringir. esfera: "U", "E", "D" ou "M". limite: entes devolvidos (padrão 20).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "siconfi_entes"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNo
buscaNo
esferaNo
limiteNo

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 cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), and the description adds real behavioral context beyond them: an empty busca returns a filtered listing rather than an error, and results are capped by limite (default 20). It still doesn't say what a returned record contains beyond the code, which is the main remaining gap.

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?

Front-loaded purpose sentence followed by a compact Args block, with no filler prose. Minor redundancy in repeating limite's default 20, which the schema already declares, but nothing wasteful.

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 simple four-parameter lookup tool with no output schema, the definition covers intent, routing to siconfi_relatorio, and every parameter. A short note on what fields come back per entity (name, UF, esfera, code) would make it fully self-sufficient.

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?

With 0% schema description coverage, the description carries the full burden and does so for all four parameters: busca accepts a name fragment or an IBGE code (with a concrete example, 'campinas') and empty means 'list by filters'; uf restricts to a state; esfera lists the actual allowed values U/E/D/M that the schema does not enumerate; limite documents the default. This is meaningfully more than the schema conveys.

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: looks up the SICONFI code for an entity (União, state, DF or municipality), and it explicitly states the output's purpose — the IBGE code is what siconfi_relatorio consumes. That single sentence distinguishes it from the sibling reporting tool without requiring the agent to inspect 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?

Implied usage is clear: call this to resolve an entity name or IBGE code before querying siconfi_relatorio, and the empty-busca case switches the tool into a filter-based listing mode. It lacks an explicit when-not-to-use (e.g. 'if you already know the IBGE code, skip this') but the routing context is unambiguous.

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