Skip to main content
Glama

Buscar licitações abertas

buscar_licitacoes
Read-onlyIdempotent

Lista licitações públicas de saúde abertas no Brasil (dados do PNCP). Filtre por estado (uf), categoria e palavra (texto). Devolve até 20 itens com link do edital original e, quando existe, o link da página da licitação no Garimpo Público.

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

Input Schema

NameRequiredDescriptionDefault
ufNoSigla do estado, ex.: PE
textoNo
limiteNo
categoriaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, closed-world), so credit goes to the added context: the PNCP provenance and the concrete return contract (up to 20 items, edital link, optional Garimpo Público page link). It omits pagination/offset behavior, 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.

Conciseness5/5

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

Two sentences, front-loaded with the resource and scope, then the filtering axes, then the return contract. No filler and nothing is buried.

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 4-parameter, all-optional search tool with no output schema, the description supplies provenance, filter semantics, and the return shape including links. Missing only result ordering and whether anything beyond the 20-item cap can be retrieved.

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 only 25% – only uf is documented in the schema – so the description must compensate. It does so partly by mapping the three meaningful filters (uf, categoria, texto) to their purpose and by tying the 20-item cap to the limite parameter, but it never explains what 'abertas' means temporally or how results are ordered.

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?

States a specific verb and resource: 'Lista licitações públicas de saúde abertas no Brasil', plus the data source (PNCP). This clearly separates it from detail-lookup siblings like ver_licitacao or ver_orgao, though no sibling is named explicitly.

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 shows the available filters (uf, categoria, texto) so an agent can infer this is the search/list entry point, but it never states when to use it instead of ver_licitacao or preco_referencia, and gives no exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources