Skip to main content
Glama

Przetargowy Janusz — Polish public tenders

Wyniki przetargów

get_tender_results
Read-onlyIdempotent

Award results of up to 10 tenders at once, by public slug (from search_archived_tenders or any other listing) — to compare prices of similar past tenders. For each: title, contracting authority, estimated value, submission deadline, public URL, and the same award results get_tender returns (winner, value, number of offers, offer price band, the winner's own offer price, rejected offers, whether the cheapest offer won), without the AI summary. results is empty when no award is known; found is false for a slug that is not public. winners lists every winner by part as the tender's public page and the search_archived_tenders card show them (company, NIP, value in PLN only where reliable, award date) — use it for prices when a tender has parts. results names the same winner as winners; when different companies won different parts, its winner_name says so and winners lists them. Requires OAuth authentication and a trial or paid plan.

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": {
      "slugs": "<slugs>"
    },
    "name": "get_tender_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYespublic_slug values from listing results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds genuinely new behavior: empty `results` when no award exists, `found=false` for non-public slugs, per-part `winners` semantics, and the OAuth plus trial/paid plan requirement. That auth gating is exactly the kind of context annotations cannot express.

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?

Front-loads the verb, resource, and batch limit before the alternative source, and each clause carries substance (return fields, edge cases, per-part behavior). The single dense paragraph is long, but almost every sentence earns its place given there is no output 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 does the full job of enumerating return fields (title, authority, estimated value, deadline, URL, award results) and the edge-case sentinels (`results` empty, `found` false, `winners` per part). Nothing an agent needs to interpret the response is missing.

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% and the single `slugs` parameter is documented in the schema, but the description still adds value by pinning the origin of slug values to listing results and reinforcing the batch limit implied by maxItems: 10. Sits above the high-coverage baseline.

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 precise verb and resource — fetch award results for up to 10 tenders by public slug — and explicitly distinguishes itself from get_tender (batch, no AI summary) and from search_archived_tenders (the source of slugs). An agent can route here without opening either sibling schema.

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?

Gives a clear use case ('to compare prices of similar past tenders') and tells the agent where slugs come from ('from search_archived_tenders or any other listing'), plus how it differs from get_tender. It stops short of explicit when-not conditions, but the context is actionable.

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