Skip to main content
Glama

Pt Announcement Search

pt_announcement_search
Read-onlyIdempotent

Search PORTUGUESE public-procurement tender ANNOUNCEMENTS (contract notices) published through Portal BASE (base.gov.pt), run by IMPIC (Instituto dos Mercados Públicos, do Imobiliário e da Construção). IMPIC's own live API needs registration and a token Pipeworx does not hold yet, so this answers from a refreshed recent-window dataset (see data_as_of and the window fields in the response). Filter by free-text keyword (matched against the Portuguese notice title), CPV classification code or prefix (e.g. "45" for construction, "72000000" for IT services), contracting-authority (buyer) name substring (Portuguese spelling, e.g. "Câmara Municipal", "Instituto"), and a publish-date range. Returns compact shaped notices: id, IMPIC notice id, buyer, title, notice type, contract type(s), base amount (EUR), CPV, publish date, and proposal deadline. Call pt_announcement_detail with the returned id for the full record.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 5,
      "query": "seguros",
      "date_to": "2026-01-31",
      "date_from": "2026-01-01"
    },
    "name": "pt_announcement_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpvNoCPV classification code or numeric prefix, e.g. "45" (construction works), "72000000" (IT services).
buyerNoContracting-authority (buyer) name, partial match, Portuguese spelling, e.g. "Câmara Municipal de Lisboa", "Instituto", "Universidade".
limitNoMax notices to return (default 20, max 100). Newest-first.
queryNoKeyword(s), case-insensitive, matched against the Portuguese notice title, e.g. "limpeza", "software", "obras", "manutenção".
date_toNoLatest PUBLISH date, YYYY-MM-DD. Defaults to the newest date in the loaded window (see ann_window_to in any response), which can trail today because IMPIC publishes per-year bulk files.
date_fromNoEarliest PUBLISH date, YYYY-MM-DD. Defaults to 90 days before date_to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds meaningful behavioral context beyond that: the live IMPIC API needs a token Pipeworx lacks, results come from a refreshed recent-window dataset that can trail today, and data_as_of/ann_window_to fields expose the staleness. It stops short of describing pagination or rate limits.

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?

A single dense paragraph, well front-loaded with the source and provenance before the filter and return-value details. It is information-rich and mostly earns its length, though the CPV and buyer examples duplicate the schema and could be trimmed.

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?

With no output schema, the description carries the return-value burden and does so by enumerating the shaped fields (id, IMPIC id, buyer, title, notice type, contract types, base amount, CPV, publish date, proposal deadline). Combined with the data-freshness caveat and the detail-tool handoff, an agent has everything needed to call and interpret the result.

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 description coverage is 100% and the schema already documents every parameter, including CPV prefix examples, buyer Portuguese spelling, and date defaults. The description restates rather than extends this, so the baseline 3 for high-coverage schemas applies.

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?

States a precise verb+resource: searching Portuguese public-procurement tender ANNOUNCEMENTS (contract notices) from a named source (Portal BASE / IMPIC). It names the sibling pt_announcement_detail and the escalation path, and the announcement-vs-full-record distinction is unambiguous.

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?

Explains the concrete filters (keyword, CPV, buyer, date range) and routes to pt_announcement_detail for the full record, giving clear context for when this tool fits. It does not, however, contrast with the sibling pt_contract_search, leaving the agent to infer announcement-vs-contract scope.

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.