Skip to main content
Glama

tenderkit

search_notices

Find cached notices by a named profile or explicit filters.

Regions are buyer TERYT voivodeship codes; 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. Use term for substrings. keyword_matches identifies the configured inclusion terms and fields that matched.

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
offsetNo
profileNo
regionsNo
currencyNoPLN
value_maxNo
value_minNo
exclude_cpvNo
keywords_anyNo
notice_typesNo
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 observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does add meaningful semantics: region codes are buyer TERYT voivodeship codes, unknown fields do not match constrained filters, no currency conversion occurs, exclude_cpv excludes notices whose every code is excluded, and keyword matching behavior is explained. It still omits pagination, ordering, and cache-freshness behavior.

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 short and front-loaded, with the core purpose in the first sentence and filter semantics organized into separate lines. Every sentence adds useful information without redundant restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex with 17 optional parameters and no annotations, and an output schema exists so return values need not be explained. The description covers several important filter behaviors but is not complete enough for an agent to confidently use the many undocumented parameters or understand pagination and ordering.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 17 parameters, so the description must compensate. It explains regions, currency, exclude_cpv, and keywords_any, but leaves many parameters such as cpv, start, end, limit, offset, value_min, value_max, profile, notice_types, and deadline fields undocumented.

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 verb and resource: 'Find cached notices' via either a named profile or explicit filters. This distinguishes the two search modes, though it does not explicitly separate this tool from siblings like search_results, get_notice, or procedure_results.

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 phrase 'by a named profile or explicit filters' implies how to invoke the tool in two modes, and the filter-behavior notes imply constrained usage. However, there is no explicit when-to-use or when-not-to-use guidance relative to the sibling tools.

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.