Skip to main content
Glama

Lithuania Public Procurement

Search active Lithuanian public tenders

search_tenders
Read-onlyIdempotent

Searches open public procurement notices in Lithuania (EU TED + national CVP IS) by keywords, CPV code, region, estimated value and submission deadline. Each result has a link to the original notice. Ieško aktyvių Lietuvos viešųjų pirkimų.

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 codes or prefixes, comma-separated, e.g. "72" (all IT services), "45233000", "79340000,79341000". Use list_cpv to find codes.
sortNodeadline (soonest first, default), published (newest first), value (largest first).
textNoKeywords in Lithuanian (or English for TED notices), e.g. "kelių remontas", "programinė įranga". All words must match; endings are ignored.
buyerNoContracting authority name contains, e.g. "Kauno miesto savivaldybė".
limitNoResults per page (default 20).
offsetNoSkip this many results (paging).
regionNoNUTS code LT011…LT029 or county name, e.g. "Kauno", "Vilniaus apskritis".
sourceNoOnly one source: TED (EU, above thresholds) or CVP IS (Lithuanian national system).
max_valueNoMaximum estimated value, EUR.
min_valueNoMinimum estimated value, EUR (notices without value are excluded).
deadline_toNoSubmission deadline until (YYYY-MM-DD).
contract_typeNoType of contract.
deadline_fromNoSubmission deadline from (YYYY-MM-DD). Default: now (only open tenders).
published_fromNoPublished on or after (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context — that each result carries a link to the original notice and that coverage spans two distinct procurement systems. It says nothing about result volume, paging behavior beyond the schema, or latency.

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?

Two sentences, front-loaded with the corpus and filter dimensions, then the useful return detail about links to original notices. The trailing Lithuanian sentence largely restates the first sentence, which is a small redundancy but may serve multilingual matching.

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

Completeness4/5

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

For a 14-parameter, zero-required search tool with no output schema, the description covers corpus, sources, filter surface and result shape well enough to call it correctly, with the schema handling per-parameter detail. It would be stronger if it stated the default behavior (all-open tenders) and how the two sources differ in coverage.

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%, so every parameter including CPV syntax, NUTS codes, sort enum and value ranges is already documented in the schema. The description only enumerates the filter categories (keywords, CPV, region, value, deadline) without adding format or precedence rules, so the baseline of 3 applies.

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 opens with a specific verb and resource ('Searches open public procurement notices in Lithuania') and names both data sources (EU TED + national CVP IS) plus the filter dimensions, so the agent knows exactly what corpus is being queried. It does not explicitly differentiate from siblings such as get_tender or changes_since, so it stops short of a 5.

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?

Usage is only implied: 'Searches open ... notices' suggests discovery/browsing use, and the schema's reference to list_cpv hints at a follow-up tool. There is no statement of when to prefer this over get_tender for detail or changes_since for incremental updates, and no exclusions.

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