aukro-mcp

Aukro Search Autocomplete, User Lookup & Popular Searches

aukro_autocomplete

Read-onlyIdempotent

Get search suggestions for Aukro.cz items, categories, landing pages, seller usernames, or trending popular searches; choose the mode to target the needed suggestion type.

Instructions

Get instant search suggestions on Aukro.cz for items, categories, and landing pages (mode: 'ALL'), autocomplete seller usernames (mode: 'USERS'), or list trending popular searches (mode: 'POPULAR'). Works anonymously.

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": "aukro_autocomplete"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	Suggestion mode: ALL (items/categories/landing pages), USERS (seller username prefix), or POPULAR (trending searches)	ALL
`text`	No	Query text prefix (required for ALL and USERS modes)
`subbrand`	No	Marketplace subbrand scope	BAZAAR
`categoryId`	No	Optional category ID scope for ALL mode

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds one piece of real behavioral context the annotations do not: 'Works anonymously,' telling the agent no credentials are needed. Beyond that it says nothing about rate limits, result counts, or response shape.

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?

A single sentence front-loads the core action, then walks the three modes in parallel structure and closes with the anonymous-access note. Every clause carries information; there is no filler.

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 four-parameter, fully documented read tool with annotations covering safety and no output schema to explain, the description covers purpose, mode routing, and auth requirements. The remaining gaps (return structure, suggestion limits, validity of text in POPULAR mode) are minor but would help an agent predict results.

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 100%, including enum documentation for mode and subbrand, so the schema already carries parameter meaning. The description's mode breakdown largely restates the mode enum rather than adding new semantics such as prefix-length limits or how categoryId interacts with the USERS/POPULAR modes. Baseline 3 is appropriate.

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 concrete verb and resource ('Get instant search suggestions on Aukro.cz') and breaks the scope into three named modes (ALL for items/categories/landing pages, USERS for seller usernames, POPULAR for trending searches). What it does is unambiguous. It stops short of explicitly contrasting itself with the closest sibling, aukro_search_offers, so an agent must infer that this returns prefixes rather than actual offer results.

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?

Gives clear per-mode selection context: use ALL for item/category/landing-page suggestions, USERS for seller username prefixes, POPULAR for trending searches. That is genuinely useful routing within the tool. It offers no when-not guidance and never names an alternative tool, so an agent deciding between this and the full search tool gets no explicit direction.

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