Skip to main content
Glama

Przetargowy Janusz — Polish public tenders

Pliki przetargu w archiwum

list_tender_files
Idempotent

Files in the document archive of one tender from the signed-in company's 'Moje przetargi' (tender_id): the tender's documents copied in (copied on the first call when the archive has none yet, as opening the tender in the app does), the company's uploads and the documents Janusz filled — with type, version and date. Read one with get_tender_file. 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": {
      "tender_id": "<tender_id>"
    },
    "name": "list_tender_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
tender_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Adds genuinely non-obvious behavior beyond the annotations: the first call may copy tender documents into the archive if it is empty, which explains why readOnlyHint=false on an ostensibly listing tool. It also discloses OAuth authentication and a trial/paid plan requirement, plus the returned fields (type, version, date). No pagination, result-size, or ordering behavior is mentioned.

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?

A single front-loaded sentence that puts the resource and scope first, then the file origins, then the read-alternative and prerequisites. It is dense and slightly run-on, but every clause carries information.

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 supplies the return shape (type, version, date) and covers auth, plan gating, and the archive-population side effect. Missing only edge-case behavior (tender not in 'Moje przetargi', empty archive after copy, result limits) for a tool that mutates state on first call.

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 0% and the schema only constrains tender_id to a UUID, so the description must carry the meaning — and it does, clarifying that the ID identifies a tender in the user's 'Moje przetargi' archive rather than any arbitrary tender. It does not state what happens when the ID is not in the company's saved tenders.

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?

Names the concrete resource (files in the document archive of one tender) and the scope ('Moje przetargi' of the signed-in company), which an agent can act on directly. It also enumerates the three file origins (copied-in, company uploads, Janusz-filled documents). It does not distinguish itself from the sibling get_tender_documents, which an agent could easily confuse with this tool.

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?

Explicitly routes content retrieval to get_tender_file ('Read one with get_tender_file'), so the list-vs-read split is unambiguous. It also states the precondition that the tender must belong to the signed-in company's saved tenders. It gives no guidance on when to prefer get_tender_documents or get_tender_file's metadata path instead.

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