aukro-mcp

Place Bid or Pre-Check Bidding on an Auction

aukro_place_bid

Destructive

Place a maximum proxy bid on an Aukro.cz auction, or use dry-run mode to check current price, minimum next bid, and bidder restrictions before bidding.

Instructions

Place a maximum proxy bid (příhoz) on an Aukro.cz auction (POST /offers/{offerId}/bid?fastBid=false), or run a safe pre-check (dryRun: true) to verify current price, minimum next bid, and whether your account has any bidder restrictions on the item. Requires authentication.

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": {
      "offerId": "<offerId>",
      "amount": "<amount>"
    },
    "name": "aukro_place_bid"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	Yes	Maximum bid amount in the specified currency (e.g. 250)
`dryRun`	No	When true, checks live offer status, minimum required bid, and bidder restrictions WITHOUT placing an actual bid
`offerId`	Yes	Numeric auction offer ID
`tfvCode`	No	Optional 4-digit SMS verification code (`X-Aukro-TFV-Code`) if requested by Aukro
`currency`	No	Bid currency (defaults to CZK)	CZK

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already flag destructive, non-idempotent, open-world behavior, and the description adds real context beyond them: authentication is required, the bid is a *proxy* maximum (Aukro bids incrementally on your behalf), and dryRun is a no-side-effect path. It does not spell out irreversibility, outbid behavior, or what a successful live bid returns, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the primary action, with the dry-run alternative and the auth requirement appended compactly. No filler or restatement of the title.

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?

For a 5-parameter mutation tool with no output schema, the description covers auth, both operating modes, and what the pre-check reports. The main gap is the outcome of a live bid (success response, immediate outbid, error on too-low amount), which an agent would want before invoking.

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 coverage is 100%, so amount, dryRun, offerId, tfvCode, and currency are all already documented, making 3 the baseline. The description adds only the `fastBid=false` detail (not a schema parameter) and the word 'maximum' reinforcing proxy semantics; it says nothing about tfvCode or currency handling that the schema doesn't already cover.

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?

The description names a specific verb and resource ('Place a maximum proxy bid (příhoz) on an Aukro.cz auction') and even pins the underlying endpoint, plus it distinguishes the two modes (live bid vs. dryRun pre-check). No sibling tool places bids, so an agent can identify this unambiguously from the tool list.

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?

It explicitly states the condition that selects each mode: place a bid normally, or set `dryRun: true` to safely verify price, minimum next bid, and bidder restrictions before committing. It does not address when to prefer a sibling such as aukro_bargain_offer or what to do if the account is restricted, so it stops short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.