aukro-mcp

Batch Poll Live Status of Multiple Offers

aukro_get_offers_status_batch

Read-onlyIdempotent

Poll live status for up to 50 offer IDs in one request to get state, price, bid count, highest bidder, and ending time.

Instructions

Quickly poll live status (state, price, nextBidMinAmount, biddersCount, highestBidderAnonymizedLogin, endingTime) for up to 50 offer IDs in a single lightweight request.

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": {
      "offerIds": "<offerIds>"
    },
    "name": "aukro_get_offers_status_batch"
  }
}

Input Schema

Name	Required	Description	Default
`currency`	No	Override response currency
`offerIds`	Yes	List of numeric offer IDs to check

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description's genuinely useful addition is the enumeration of the returned fields (`state`, `price`, `nextBidMinAmount`, etc.), which compensates for the absent output schema, but it says nothing about rate limits, per-ID failure handling, or whether the 'lightweight' claim implies caching.

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?

One sentence, front-loaded with the verb and purpose, with the returned-field list inline rather than as a separate block. There is no filler wording to remove.

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 two-parameter read-only polling tool with no output schema, the description supplies the key missing piece: what each returned record contains. It stops short of documenting the currency override or behavior when some IDs are invalid/delisted, but nothing essential to invoking it correctly is absent.

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 the schema already documents both parameters, making 3 the baseline. The description reinforces the offerIds semantics ('up to 50 offer IDs') but says nothing about the `currency` override, leaving that parameter's intent entirely to the schema.

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?

States a specific verb ('poll') plus resource ('live status of offers') and a batch scope ('up to 50 offer IDs'), which separates it from aukro_get_offer_detail and aukro_get_offer_bids_and_similar by implication. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

'Quickly poll' implies a repeated/live-checking use case, and the 50-ID batch framing hints at bulk monitoring rather than single-offer inspection. However, there is no explicit when-to-use/when-not or named alternative such as aukro_get_offer_detail for a single offer.

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