Skip to main content
Glama

Przetargowy Janusz — Polish public tenders

Ustaw dane do wypełnienia

set_fill_details
DestructiveIdempotent

Sets the details Janusz needs to fill in the documents of a tender in 'Moje przetargi' — the completion deadline, the signatory's name and role, and the VAT rate of the offer price — as the user stated them (the same details the Janusz chat in the app records). Only the given fields change. Returns what is still missing before start_fill; the offer price is set with confirm_bid_price. 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": "set_fill_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
vat_rateNoVAT rate of the offer price (confirm_bid_price is net): 23, 8, 5, 0 or zw (VAT-exempt). Janusz computes the gross price from it; without it he assumes 23.
tender_idYes
signatory_nameNofull name of the person signing the offer
signatory_roleNoe.g. 'Prezes Zarządu'
completion_deadlineNoe.g. '30 dni od podpisania umowy' or '2026-12-15'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / vat_rate
      Added value: +{
      +  "description": "VAT rate of the offer price (confirm_bid_price is net): 23, 8, 5, 0 or zw (VAT-exempt). Janusz computes the gross price from it; without it he assumes 23.",
      +  "enum": [
      +    "0",
      +    "5",
      +    "8",
      +    "23",
      +    "zw"
      +  ],
      +  "type": "string"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so safety is partly pre-communicated. The description usefully adds OAuth and trial/paid plan requirements, the partial-update behavior, and that it returns the list of still-missing fields. However, it never explains what destructiveHint means here — whether previously stored values are overwritten — leaving the main risk unaddressed.

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?

Core purpose is front-loaded in the first clause, with secondary constraints (partial update, return value, auth/plan) following in short sentences. The opening sentence is long and dash-laden, but every sentence carries distinct 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 correctly discloses the return value (what is still missing) and the auth/plan prerequisites, and it scopes the VAT/price split to confirm_bid_price. The one gap is destructive/overwrite behavior, which matters for a tool flagged destructiveHint=true.

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

Parameters3/5

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

Schema description coverage is 80% and the enum on vat_rate is documented in-schema with a fallback default of 23. The description lists the same three field groups but adds no format, ordering, or syntax detail beyond what the schema already supplies, so baseline 3 applies.

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 (Sets) and resource (details Janusz needs to fill in tender documents), enumerates the exact fields (completion deadline, signatory name/role, VAT rate), and names the product surface 'Moje przetargi'. It also names the sibling that handles the offer price, so the agent can distinguish it from confirm_bid_price without opening schemas.

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?

Explains the workflow position: it reports what is still missing before start_fill, and explicitly routes price-setting to confirm_bid_price. It also clarifies partial-update semantics ('Only the given fields change'). No explicit when-not-to-use case (e.g. before add_to_my_tenders), which keeps it below 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.

Resources