Skip to main content
Glama

Przetargowy Janusz — Polish public tenders

Mój przetarg

get_my_tender
Read-onlyIdempotent

One tender from the signed-in company's 'Moje przetargi' by tender_id (from list_my_tenders or list_matched_tenders): pipeline status and its history, deadlines, the AI summary state (ready / requested / no_documents / none), the number of tender documents and archive files, the last document fill run, what filling in its documents still needs (fill_details: missing details, confirmed values, Janusz's price proposals), and links to its workspace in the app, its public page and its page on the source portal (source_url, where the official documents are). The summary's text itself comes from get_tender with the returned slug. 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": "get_my_tender"
  }
}

Input Schema

NameRequiredDescriptionDefault
tender_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuine context beyond them: authentication and plan requirements, and the enumerated AI summary states (ready / requested / no_documents / none) that shape what an agent will see. It stops short of describing error behavior for a missing or unauthorized tender.

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 front-loaded sentence that puts purpose and scope first, then the payload enumeration, then the sibling pointer and prerequisites. It is dense but every clause corresponds to a real returned field; the long mid-sentence enumeration of return values is the only source of friction.

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 entire burden of explaining what comes back, and it does so field-group by field-group. Combined with the stated auth/plan prerequisites and the pointer to get_tender for the summary text, nothing an agent needs in order to call this correctly 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 description coverage is 0% for the single parameter, so the description must carry the meaning, and it does: it explains that tender_id is a tender identifier coming from list_my_tenders or list_matched_tenders, which tells the agent where to obtain a valid UUID. It does not describe format or failure on unknown IDs, but the origin guidance is the practically important part.

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 and resource ('One tender from the signed-in company's "Moje przetargi" by tender_id') and then enumerates exactly what comes back: pipeline status and history, deadlines, AI summary state, document counts, fill state, links. It also distinguishes itself from siblings get_tender (summary text), list_my_tenders and list_matched_tenders, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Gives the exact provenance of the required argument ('tender_id from list_my_tenders or list_matched_tenders') and names the alternative for a related need ('The summary's text itself comes from get_tender with the returned slug'). Prerequisites (OAuth authentication, trial or paid plan) are stated explicitly.

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