Skip to main content
Glama

emendas_pix

Read-onlyIdempotent

Query and group special federal transfer action plans from TransfereGov by state, parliamentarian, or beneficiary, filtering by year, status, and planned value.

Instructions

Emendas Pix (transferências especiais da União a estados e municípios), pelo TransfereGov.

Agrupa os planos de ação por por (uf, parlamentar ou beneficiario), ordenados pelo valor. Filtros: uf (sigla), situacao (ex.: CIENTE, IMPEDIDO), parlamentar e beneficiario (trecho do nome). Os valores são os previstos no plano de ação (custeio + investimento), não o montante já pago. Sem ano, usa o ano corrente.

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": "emendas_pix"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNo
anoNo
porNouf
limiteNo
situacaoNo
parlamentarNo
beneficiarioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, and idempotent behavior. The description adds important domain semantics beyond annotations: values are planned amounts (custeio + investimento), not already-paid amounts, and a missing year defaults to the current year. It does not explain the `limite` behavior or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a compact, front-loaded paragraph where each sentence adds useful information: purpose, grouping, filters, value caveat, and default-year behavior. There is no boilerplate or wasted wording.

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 seven-parameter read-only query tool with no output schema, the description supplies the core query semantics, data caveats, and default behavior. The missing explanation of `limite` and lack of return-field detail are minor gaps but not blockers for correct invocation.

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?

With 0% schema description coverage, the description compensates well by explaining `por` values (uf, parlamentar, beneficiario), `uf` as a state abbreviation, `situacao` examples, `parlamentar`/`beneficiario` as name fragments, and the default year. It leaves the `limite` parameter undocumented, so compensation is strong but incomplete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (Emendas Pix, special federal transfers to states and municipalities via TransfereGov) and a clear action: grouping action plans by `por` and ordering by value. It does not explicitly differentiate from sibling tools, but the domain is unique among the listed siblings.

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?

The description implies when to use the tool by explaining available filters and the default year behavior, but it gives no when-not guidance or named alternatives. Usage is inferable rather than explicitly guided.

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