Skip to main content
Glama

Search tenders

search_tenders
Read-onlyIdempotent

Search public procurement notices from CEJN by keyword, buyer, municipality, status, CPV code, date or estimated value.

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_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpvNoCPV division (2 digits) or an 8-digit code
pageNo
sortNopublicationDate
buyerNo
limitNo
queryNoKeywords; a comma or semicolon separates alternatives
dateToNo
statusNo
dateFromNo
minValueNo
municipalityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world source, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that: no mention of the hard result caps implied by the schema (limit max 25, page max 20), no default sort, no statement about how paging terminates, and no note about the source's freshness or coverage.

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 tight sentence with the resource and the filter surface front-loaded and no filler. It is efficient, though one flat clause for eleven parameters gives the reader no structural grouping between filtering, sorting and paging.

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

Completeness2/5

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

For an eleven-parameter search tool with no required arguments, no output schema and thin schema documentation, the description is under-specified: an agent cannot tell from it what a result contains, how many pages are available, what order results arrive in, or how minValue and the date range are interpreted. Annotations cover only safety, so the descriptive burden remains largely unmet.

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 only 18%, so the description must carry meaning, and it does name most filter concepts (keyword, buyer, municipality, status, CPV code, date, estimated value) which maps roughly onto query, buyer, municipality, status, cpv, dateFrom/dateTo and minValue. It leaves real ambiguity unresolved: which date field dateFrom/dateTo constrain (publication vs deadline), that minValue is a lower bound only with no upper bound, and it says nothing at all about sort, page or limit.

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 gives a specific verb ('Search') plus resource ('public procurement notices from CEJN') and enumerates the filter dimensions, so an agent knows this is the keyword/facet search over the tender corpus. It stops short of naming a sibling such as get_tender (single record) or search_public_payments, so the boundary is only implicitly drawn from the resource noun.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the sibling tools that overlap (get_tender for a known notice, search_companies, search_public_payments). The list of filterable dimensions hints at useful contexts but leaves the agent to infer them.

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