Skip to main content
Glama

Brazil Pncp

by io.github.pipeworx-io
OverviewAdmin

Brazil Search Tenders

brazil_search_tenders
Read-onlyIdempotent

Search published Brazilian government tenders / bidding notices (contratações / editais) from the official PNCP portal (Portal Nacional de Contratações Públicas). These are open or recently published procurement opportunities under Lei 14.133/2021. Returns each tender with its PNCP control id, object (Portuguese), estimated value in BRL, procurement modality, agency, state/municipality, proposal open/close dates, and a link to the source system. Dates are YYYYMMDD filtering by PNCP publication date; omit for roughly the last 30 days. The modality defaults to 6 (Pregão Eletrônico), the most common; pass another code to filter differently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based). Default 1.
date_toNoEnd date (PNCP publication) as YYYYMMDD, e.g. "20260601". Defaults to today.
modalityNoProcurement modality code (codigoModalidadeContratacao). REQUIRED by the API; defaults to 6 (Pregão Eletrônico). Others: 4=Concorrência Eletrônica, 8=Dispensa, 9=Inexigibilidade, 12=Credenciamento, 3=Concurso, 1=Leilão Eletrônico.
date_fromNoStart date (PNCP publication) as YYYYMMDD, e.g. "20260501". Defaults to ~30 days ago.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "date_from": "20260401",
+    "date_to": "20260501",
+    "modality": 6
+  },
+  {
+    "modality": 4,
+    "page": 1
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by stating the source system (PNCP) and legal framework (Lei 14.133/2021), which provides behavioral context beyond safety.

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 description is two sentences, front-loaded with purpose, and efficient. However, it could be slightly more compact by merging some details.

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?

Given no output schema, the description fully explains what is returned (PNCP ID, object, value, modality, agency, dates, link). No important details are missing for the tool's complexity.

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 coverage is 100%, but the description adds significant meaning: explains date defaults (omit for last 30 days), modality defaults to 6 with examples of other codes, and provides context for filtering. This goes beyond the schema descriptions.

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 clearly states that the tool searches published Brazilian government tenders/bidding notices from the PNCP portal, specifies the data returned, and differentiates from the sibling 'brazil_search_contracts' by focusing on tenders.

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?

The description explains that results are open/recent procurement opportunities, how date filtering works (defaults to last 30 days), and the modality default and alternatives. It does not explicitly mention when not to use this tool, but the context is clear.

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

All Brazil Pncp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources