Skip to main content
Glama

Lithuania Public Procurement

Tender details

get_tender
Read-onlyIdempotent

Returns one tender with full description, CPV codes and names, region, value, deadline and links to the original notice and PDF. id: e.g. "cvpis:10556371" or "ted:787554-2023".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_tender"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTender id from search_tenders

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 needs no restating. The description adds genuinely useful behavior beyond that: with no output schema, it is the only place that enumerates what comes back (CPV codes, region, value, deadline, and links to the original notice and PDF). It does not say what happens when an id is malformed or missing from the index.

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?

Two sentences, zero filler. The return payload is front-loaded before the id-format note, so an agent scanning the first clause already knows what the call yields.

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 one-parameter lookup with no output schema, the description covers the essentials: what is fetched, what comes back, and the accepted id shapes. The only meaningful gap is failure behavior for invalid or stale ids, which matters little because the tool is read-only and idempotent.

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 coverage is 100% and the schema already explains that id comes from search_tenders, so the baseline would be 3. The description does add real value by showing two concrete id formats (CVPI and TED styles), which is format information the schema lacks, so this sits at the upper end of the adequate band.

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 cardinality ("Returns one tender") and then enumerates the payload: full description, CPV codes and names, region, value, deadline, and links to the original notice and PDF. That clearly separates a single-record fetch from the plural search_tenders sibling, though the sibling is never named explicitly.

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: an agent can infer this is the follow-up call once it has an id, and the description gives id formats ("cvpis:10556371", "ted:787554-2023") that hint at post-search retrieval. There is no explicit when-to-use vs. when-not statement, no mention that this is the step after search_tenders, and no guidance on error cases for unknown ids.

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