Skip to main content
Glama

List My Seller Offers, Sold Items & Sale Transactions

aukro_my_sales
Read-onlyIdempotent

Inspect your Aukro.cz seller inventory and orders, including active listings, sold or unsold offers, scheduled offers, and sale transactions. Requires authentication.

Instructions

Inspect your seller inventory and orders on Aukro.cz: active listings (view: 'ACTIVE'), sold offers (view: 'SOLD'), ended unsold offers (view: 'NOT_SOLD'), scheduled offers (view: 'SCHEDULED'), or active sale transactions/orders (view: 'TRANSACTIONS'). 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_my_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo0-indexed page number
sortNoOptional sort order (e.g. 'endingTime:ASC', 'startingTime:DESC')
viewNoSeller view to fetchACTIVE
queryNoOptional text filter on your offers
pageSizeNoNumber of items per page
categoryIdNoOptional category ID filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 adds one useful behavioral fact not in annotations: authentication is required. It says nothing about pagination behaviour, result ordering, or how result shape differs between offer views and TRANSACTIONS, which is the main remaining ambiguity for an agent.

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 front-loaded sentence that names the domain first, then the modes, then the auth prerequisite — no filler. It is slightly dense with inline code spans and parenthetical lists, but every clause carries information.

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?

For a 6-parameter read tool with no output schema, the description covers the input side adequately but leaves the return side unaddressed, and returns plausibly differ between offer views and TRANSACTIONS. Authentication and view semantics are covered; result contents and pagination expectations are not.

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?

Schema description coverage is 100%, so the baseline is 3, but the description earns an increment by translating the opaque enum values into concrete business concepts (NOT_SOLD = ended unsold offers, TRANSACTIONS = active sale transactions/orders). That meaning is not derivable from the enum names alone.

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+resource ('Inspect your seller inventory and orders on Aukro.cz') and scopes it to the authenticated seller, which separates it from the public aukro_search_offers. It enumerates all five view modes with human-readable meaning rather than just repeating enum tokens. It stops short of naming the sibling it supersedes for own-offer lookups.

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 view enumeration doubles as a when-to-use map: ACTIVE for live listings, SOLD for completed sales, NOT_SOLD for expired unsold, SCHEDULED for queued, TRANSACTIONS for orders. That is genuinely clear routing guidance. No explicit exclusions or sibling alternatives (e.g. use aukro_my_bids_and_purchases for buyer-side data, aukro_search_offers for other sellers' offers) are provided.

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