Skip to main content
Glama
VladyslavMykhailyshyn

Prozorro.Sale MCP Server

Benchmark an auction against similar ones

find_comparable_auctions
Read-onlyIdempotent

Finds comparable completed auctions for a reference lot, reporting median prices and sell rates to benchmark a bid or assess market risk.

Instructions

Takes one auction and finds recent comparable ones, then reports median prices and how often that kind of lot actually sells.

WHEN TO USE: valuation and risk questions — "is this price reasonable", "what do similar plots go for", "how likely is this to sell", "should I bid at the starting price".

KEY PARAMETERS

  • auction (required): the reference auction — public auction id or procedure id.

  • match_on: what a comparable must share. Default ["sellingMethod","classification"]. sellingMethod — same auction format and programme classification — same CAV asset category region — same oblast; add this for a local benchmark, which is usually what is wanted valueRange — within ±50% of the starting price; use to exclude outliers Adding more criteria gives a tighter but smaller sample.

  • concluded_only: default true — compares only against finished auctions, which is what a price benchmark needs. Set false to also see what is currently on the market.

  • limit / scan_pages: widen the sample when comparableCount comes back low.

EXAMPLE — price benchmark for a land lease: {"auction":"LRE001-UA-20260708-03894","match_on":["sellingMethod","classification"]}

EXAMPLE — what similar assets are on the market right now: {"auction":"SPD001-UA-20260806-70620","concluded_only":false,"limit":25}

RETURNS: the reference summary, median starting and achieved prices, sold share, and the comparable auctions themselves. Re-listings of the same lot are excluded so one asset is not counted twice. The sample comes from recent activity, not full history — say so when quoting a figure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum comparables to return. Default 15.
auctionYesReference auction — public auction id (e.g. "LRE001-UA-20260708-03894") or 24-character procedure id.
match_onNoWhich attributes a comparable must share. Default ["sellingMethod", "classification"]. Add "region" for local benchmarks, "valueRange" to stay within ±50% of the starting price.
scan_pagesNoFeed pages to scan when a broad search is needed. Default 8.
concluded_onlyNoOnly compare against auctions that already finished (complete or unsuccessful), which is what a price benchmark needs. Default true.
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so the bar is lower. The description adds valuable context beyond annotations: 'Re-listings of the same lot are excluded' and 'The sample comes from recent activity, not full history — say so when quoting a figure.' These are important behavioral caveats not evident from the schema.

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?

The description is organized with clear sections: core purpose, when-to-use, key parameters, examples, and returns. Each section is concise and every sentence adds value. Despite its length, it never feels padded, and the examples are well-integrated.

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

Completeness5/5

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

With 5 parameters, no output schema, and moderate complexity, the description covers usage, parameter semantics, return contents, and important caveats (re-listing exclusion, recency). It even advises how to communicate results to users ('say so when quoting a figure'), making it complete for an agent to invoke correctly.

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

Parameters5/5

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

Schema description coverage is 100%, but the description greatly enriches parameter meaning: explains each match_on enum option ('same auction format and programme', 'same CAV asset category', 'region — same oblast', 'valueRange — within ±50%'), explains the impact of adding criteria, and clarifies concluded_only and limit/scan_pages. The examples further illustrate parameter combinations.

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?

The description opens with a specific verb+resource: 'Takes one auction and finds recent comparable ones, then reports median prices and how often that kind of lot actually sells.' This clearly distinguishes it from sibling tools like search_auctions (searching) or get_auction (fetching a single record).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

An explicit 'WHEN TO USE' section states 'valuation and risk questions' and gives concrete example queries. It does not mention when not to use or name alternatives among sibling tools, so it falls short of a 5 but is clearly actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VladyslavMykhailyshyn/prozorro-sale-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server