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 2021 county code: LT011 Vilniaus, LT021 Alytaus, LT022 Kauno, LT023 Klaipėdos, LT024 Marijampolės, LT025 Panevėžio, LT026 Šiaulių, LT027 Tauragės, LT028 Telšių, LT029 Utenos — or the county name, e.g. "Kauno".
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. Changed1 schema field changed
    • changedInput schema / properties / region / description
      Previous value: -"NUTS code LT011…LT029 or county name, e.g. \"Kauno\", \"Vilniaus apskritis\"."New value: +"NUTS 2021 county code: LT011 Vilniaus, LT021 Alytaus, LT022 Kauno, LT023 Klaipėdos, LT024 Marijampolės, LT025 Panevėžio, LT026 Šiaulių, LT027 Tauragės, LT028 Telšių, LT029 Utenos — or the county name, e.g. \"Kauno\"."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — 'Each result has a link to the original notice' — which matters because there is no output schema. It does not disclose pagination defaults, total-count behavior, or what happens when a notice lacks an estimated value (that constraint lives only in the min_value schema text).

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?

The core is a single front-loaded sentence that packs sources, geography and filter dimensions efficiently, followed by one short caveat about result links. The trailing Lithuanian sentence merely duplicates the tool's purpose for human readers and adds nothing for an agent, but it is short and does not obscure the lead.

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?

With 14 parameters and no output schema, the description does the minimum: it identifies the sources and confirms results link to the original notice. It leaves the default behavior implicit in some places — that results are open tenders only (from 'open'/'active'), and paging/sorting defaults — though those are documented in the schema. Adequate, but a richer statement of what a result record contains would help given the missing output schema.

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%, including examples, NUTS codes, date formats and enum meanings, so the schema carries all parameter meaning. The description only restates the filter categories already present (keywords, CPV, region, value, deadline) and adds no syntax or interaction details such as how text matching combines with cpv. Baseline 3 is appropriate.

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 and national CVP IS) plus the filter dimensions. An agent can tell this is the discovery/search tool rather than a single-record fetch like get_tender, though it never names that sibling explicitly, so differentiation is inferred rather than stated.

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 implied by the word 'open' and by the enumeration of filters, so an agent can infer this is for finding candidate tenders. There is no explicit when-to-use/when-not guidance and no routing to alternatives such as changes_since (for updates since a timestamp) or list_cpv, which is only mentioned inside the cpv parameter schema rather than in the description.

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