Skip to main content
Glama

search_notices

Find cached public procurement notices by profile or filters, with optional refresh fetching up to 120 days. Filter by region, CPV, amount, keywords, and deadline.

Instructions

Find cached notices by a named profile or explicit filters. Optional refresh fetches at most 120 days.

    Regions are buyer voivodeships by Polish name ("mazowieckie") or TERYT code ("14");
    unknown fields do not match a constrained filter.
    Amounts must use the stated currency; no exchange-rate conversion is applied.
    CPV codes or prefixes ending in * in exclude_cpv never count; a notice whose every code is excluded is left out.
    Keywords match word starts in titles, descriptions and lot titles (lek finds leków; lek* is the same).
    Use *term* for a substring anywhere in a word. A * elsewhere is an error.
    total counts all matching saved notices. Use compact=true for notice summaries, then get_notice for details.
    notice_kinds compares normalized kinds across sources; notice_types compares raw source values.
    dedupe="procedure" groups matching publications and keeps the newest per procedure.
    open_now excludes same-day date-only deadlines and notices with no known deadline.
    keyword_matches identifies the configured inclusion terms and fields that matched.
    coverage reports the requested publication window, covered intervals, last acquisition attempt and
    acquisition status per source. Empty results outside coverage do not prove absence.
    

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

Input Schema

NameRequiredDescriptionDefault
cpvNo
endNo
limitNo
startNo
dedupeNo
offsetNo
compactNo
profileNo
refreshNo
regionsNo
currencyNoPLN
open_nowNo
value_maxNo
value_minNo
exclude_cpvNo
keywords_anyNo
notice_kindsNo
notice_typesNo
exclude_scopeNo
exclude_buyersNo
exclude_keywordsNo
deadline_max_daysNo
deadline_min_daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that results are cached, that refresh is capped at 120 days, that no FX conversion occurs, that unknown fields silently fail to match, and that a misplaced * is an error. It does not state permission or rate-limit constraints, but the caching and coverage semantics are unusually well disclosed.

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?

Purpose is front-loaded in the first two sentences, and each subsequent line carries distinct semantics rather than filler. It is dense and largely unformatted for params, so a reader must infer which parameter each note applies to.

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?

For a 23-parameter cached search with a declared output schema, the definition covers selection semantics, fetch freshness, coverage limitations, and result-shape switches (compact, dedupe, total). Return values need not be explained because an output schema exists.

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 0% across 23 parameters, so the description must compensate. It explains the tricky ones well — regions/TERYT, currency, CPV and exclude_cpv with * prefixes, keyword word-start vs substring rules, dedupe="procedure", open_now, notice_kinds vs notice_types, keyword_matches, coverage. It leaves limit, offset, start/end, value_min/value_max, deadline_min/max_days, exclude_buyers, exclude_keywords, and exclude_scope unexplained, and does not tie its notes to parameter names.

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?

"Find cached notices by a named profile or explicit filters" gives a specific verb, resource, and the two selectivity modes. It also points to get_notice for detail retrieval, which implicitly separates listing from fetching. It stops short of naming how it differs from search_results.

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?

Concrete routing guidance is present: "Use compact=true for notice summaries, then get_notice for details," plus the caveat that empty results outside coverage do not prove absence. Missing is explicit guidance on when to prefer a sibling search tool or when refresh should be avoided.

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