Skip to main content
Glama

search_auctions

Read-onlyIdempotent

List lots in Okun Koneosa's online auction (huutokauppa).

The auction sells new and used machines, tools and supplies. Use this when the customer asks about the auction, used machines or bidding. Auction lots are NOT in search_catalog: they are single items sold to the highest bidder.

Args: query: Optional Finnish keyword matched against title, description, manufacturer, model and condition. Leave empty to list all lots. limit: Maximum lots to return (1-20, default 10).

Returns: JSON with status ('open', 'coming' or 'closed'), opens_label when the auction opens later, section_url, terms_url and lots. Each lot has title, condition, current_price, min_next_bid, bid_count, ends_at, pickup_town, delivery, vat and lot_url.

Notes: - Bidding is not possible through this tool. Share lot_url; the customer bids on the lot page with their own account. - A bid in the last 3 minutes extends ends_at by 3 minutes, so prices and end times change. Fetch again rather than reusing old values. - Some used lots are sold under the margin scheme: VAT is included but not itemised, and a business buyer cannot deduct it (see vat). - For auction rules (payment, pickup, withdrawal right) use search_shop_policies_and_faqs with query "huutokauppa".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_auctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax lots (1-20)
queryNoOptional Finnish keyword, e.g. 'porakone', 'pyörä'

Output Schema

NameRequiredDescriptionDefault
lotsNo
noteYesHow the agent should present the lots to the customer
queryNo
totalYesMatching lots across all results
statusYes'open', 'coming' (opens later, see opens_label) or 'closed'
opens_atNoUTC ISO 8601 when status is 'coming'
terms_urlNoAuction terms page (when open)
opens_labelNoOpening time in Finnish
section_urlNoAuction front page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the safety hints, the description provides critical behavioral context including: bidding is impossible via this tool (requiring URL sharing), bids in the last 3 minutes dynamically extend the end time, and specific information regarding VAT treatment on used lots.

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?

The definition is highly detailed, which makes it long, but the structure is excellent. Key contextual information (scope, when to use, limits) is front-loaded, ensuring high informational value per section.

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?

Given the tool's complexities—such as real-time bidding mechanisms, external URL requirements for actual purchasing, and specific VAT rules—the definition is exhaustive and complete for an AI agent to handle complex customer intent.

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?

While the schema is fully covered, the description adds crucial semantic context by specifying that 'query' must be a Finnish keyword and provides language examples. It also adds usage context that leaving 'query' empty lists all lots.

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 clearly defines the tool's purpose: listing lots specifically in Okun Koneosa's online auction. It distinguishes this tool from the general search capabilities by stating explicitly that auction lots are not contained within search_catalog.

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?

It provides clear usage conditions ('when the customer asks about the auction, used machines or bidding') and cross-references a sibling tool for related policies ('search_shop_policies_and_faqs'). This makes it easy for an agent to route the query correctly.

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