Skip to main content
Glama

Prozorro Sale Procedure

prozorro_sale_procedure
Read-onlyIdempotent

Full detail of one Prozorro.Sale auction by its public auction id (e.g. "LRE001-UA-20260813-89379") or internal 24-hex id: items (cadastral numbers, areas, addresses), start price, guarantee, bids with amounts and bidder organisations, awards, signed contracts, cancellations, related registry assets, and the REPEAT-AUCTION CHAIN (earlier failed attempts and later repeats of the same lot). Protected-record flags are passed through verbatim.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "LRE001-UA-20260813-89379"
    },
    "name": "prozorro_sale_procedure"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPublic auction id (e.g. LRE001-UA-20260813-89379) or the 24-hex internal id.
include_chainNoWalk the repeat-auction chain (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds real behavioral context beyond them: the response bundles items, prices, guarantee, bids with bidder organisations, awards, contracts, cancellations, registry assets, the repeat-auction chain, and notes that protected-record flags are passed through verbatim. It stops short of stating size limits, pagination of bids, or any auth/privacy handling.

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?

One dense but front-loaded sentence: identity first, then the returned payload. Every clause earns its place by enumerating distinct returned sections; only the parenthetical id example is mildly redundant with the schema.

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 no output schema, the description carries the burden of describing returns and does so comprehensively — items, pricing, bids, awards, contracts, cancellations, assets, chain, and flag passthrough. For a read-only two-parameter lookup, an agent has enough to call it and interpret the result.

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 100%, so baseline is 3; the description still adds value by explaining what the repeat-auction chain means ('earlier failed attempts and later repeats of the same lot') for include_chain, and by repeating the accepted id formats. Marginal but genuine added meaning over the schema text.

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+resource+scope: 'Full detail of one Prozorro.Sale auction by its public auction id or internal 24-hex id.' The 'one ... by id' framing clearly distinguishes it from the sibling search/changes/asset tools without needing to name them. An agent can tell this is a single-record detail lookup.

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?

Clear context for use: you need an auction identifier (public id or 24-hex internal id) to call it, and it returns one record's full detail. No explicit exclusions or named alternatives (e.g. 'use prozorro_sale_search to find an id'), which keeps it short of a 5.

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.