aukro-mcp

Read, Search & Send Aukro Messages (Moje zprávy)

aukro_messages

Manage Aukro.cz buyer and seller conversations: list threads and unread counts, search messages, read message history, reply to threads, or ask sellers about offers.

Instructions

Manage buyer/seller conversations on Aukro.cz: list message threads and unread count (LIST), search conversations (SEARCH), read message history in a thread (READ_THREAD), reply to a thread (REPLY), or ask a seller a question about an offer (ASK_ITEM_QUESTION). Requires authentication.

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_messages"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	0-indexed page number
`extId`	No	Conversation thread external ID (`extId`, for `READ_THREAD` and `REPLY`)
`action`	No	Messaging action	LIST
`offerId`	No	Offer ID when asking a seller a question (`ASK_ITEM_QUESTION`)
`pageSize`	No	Messages or threads per page
`searchTerm`	No	Search query string (for `SEARCH`)
`messageBody`	No	Message text content (for `REPLY` or `ASK_ITEM_QUESTION`)

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 the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), and the description adds the useful 'Requires authentication' prerequisite. It does not disclose the consequences of REPLY/ASK_ITEM_QUESTION (a message is actually sent, non-idempotent), what LIST returns besides an unread count, or pagination behaviour, which are the gaps left for a 7-param multi-action tool.

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?

A single sentence with the resource stated first and the action modes grouped afterwards — front-loaded and waste-free. The parenthetical action list partially duplicates the enum already in the schema, which keeps it just short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 0 required parameters spread across five actions, the critical missing piece is which parameters become mandatory per action (extId for READ_THREAD/REPLY, offerId and messageBody for ASK_ITEM_QUESTION) and any return shape, since there is no output schema. Auth requirement is covered, so this is adequate but incomplete for a multiplexed tool.

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% and each parameter description already names the action it belongs to (extId for READ_THREAD/REPLY, offerId for ASK_ITEM_QUESTION). The description reinforces that mapping but adds no format, constraint, or conditional-requirement detail beyond the schema. 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 and resource (manage buyer/seller conversations on Aukro.cz) and enumerates the distinct operations the single tool exposes. No sibling tool covers messaging, and the action list makes the tool's scope unambiguous.

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?

The per-action breakdown implicitly tells the agent which action to pick for list/search/read/reply/ask, which is the main routing decision here. However, it gives no explicit guidance on when to use this tool versus siblings such as aukro_my_account or aukro_search_offers, nor any exclusions or prerequisites beyond the auth note.

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