Skip to main content
Glama

Lithuania Public Procurement

New, changed and closed tenders since a time

changes_since
Read-onlyIdempotent

Returns tenders that were added, changed or closed after the given time (up to 30 days back), oldest change first. Use next_cursor from the response to continue. Optional cpv filter.

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

Input Schema

NameRequiredDescriptionDefault
cpvNoCPV codes or prefixes, comma-separated, e.g. "72" (all IT services), "45233000", "79340000,79341000". Use list_cpv to find codes.
limitNo
sinceNoISO time, e.g. 2026-11-20T00:00:00Z
cursorNonext_cursor from a previous call (instead of since)

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 genuinely adds beyond that: a hard 30-day lookback cap and oldest-change-first ordering are real behavioral traits. It stops short of describing termination of the cursor loop or response shape, so it goes beyond the minimum but is not rich.

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 with the primary behavior front-loaded and the pagination hint second; no filler. The 'Optional cpv filter' fragment is slightly redundant given the schema but costs little.

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 usefully points at next_cursor in the response, and the 30-day limit plus change ordering cover the main behavioral unknowns for a 4-param read tool. Remaining gaps — loop termination and behavior when since and cursor are combined — are moderate but not blocking.

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 75%, so most parameters are already documented by the schema, including cursor's 'instead of since' mutual exclusion and cpv's list_cpv pointer. The description only restates that cpv is optional and that next_cursor drives continuation, adding no format or precedence detail beyond the schema.

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?

States a specific verb and resource — returns tenders added, changed or closed after a time — and adds scoping detail (30-day window, change-order) that an agent can use to distinguish this change-feed from a search tool. It never names search_tenders or get_tender, so the sibling differentiation is only inferable from behavior.

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?

The incremental-sync use case is implied by 'since' plus 'Use next_cursor from the response to continue', and the cpv filter is flagged as optional. However, it gives no explicit when-to-use versus search_tenders, and does not say what happens if both since and cursor are supplied or how to know you have reached the end.

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