Skip to main content
Glama

Lithuania Public Procurement

Find CPV (BVPŽ) codes

list_cpv
Read-onlyIdempotent

Finds CPV codes by words (Lithuanian names from CVP IS, English for divisions) or by code prefix, with the number of active tenders for each code. Empty query lists the 45 top-level divisions. Free.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoe.g. "valymo paslaugos", "software", "45"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent, closed-world read, so the description's job is to add context and it does: per-code active tender counts are returned, empty query yields the 45 top-level divisions, names are Lithuanian from CVP IS with English for divisions, and calls are free. It stops short of disclosing pagination or iteration 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?

One dense sentence followed by a one-word cost signal; the core capability, both input modes, the return payload, and the empty-query edge case all land up front with no filler.

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?

With no output schema, the description correctly carries the return-shape burden (codes plus active tender counts) and covers the degenerate empty-query case. What is missing is a default or upper-bound explanation for `limit`, the one unaddressed control in a two-parameter tool.

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

Parameters4/5

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

Schema coverage is only 50%, but the description compensates meaningfully for `query` by explaining that it accepts words in specific languages or a code prefix, and that empty input triggers division listing. The `limit` parameter is left undocumented in both the description and schema, which is the remaining gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: finds CPV (BVPŽ) codes by words or code prefix, and adds the payload content (active tender counts per code). This is clearly distinguishable from the tender-oriented siblings (search_tenders, get_tender, changes_since) as a reference lookup.

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 through two behavioral hints: an empty query browses the 45 top-level divisions, and 'Free' signals no cost concern. There is no explicit guidance on when to prefer this over search_tenders, nor any prerequisite or when-not statement, so the agent must infer the discovery-then-search workflow itself.

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