aukro-mcp

Get Category Filter Attributes & Parameters

aukro_get_category_attributes

Read-onlyIdempotent

Retrieve filterable attributes and their allowed option keys for a category ID, then use the returned IDs and keys to build accurate attribute filters for offer searches.

Instructions

Retrieve all filterable/exposable attributes (e.g. Condition / Stav zboží, Brand, Storage, Material) and their allowed option keys for a given categoryId. Use the returned attributeId and allowedValues[].key values in aukro_search_offers's attributeFilters parameter.

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": {
      "categoryId": "<categoryId>"
    },
    "name": "aukro_get_category_attributes"
  }
}

Input Schema

Name	Required	Description
`categoryId`	Yes	Numeric category ID (e.g. 107152 for iPhone)
`searchQuery`	No	Optional case-insensitive filter on attribute name (e.g. 'model', 'stav', 'kapacita')
`onlyImportant`	No	When true, returns only mandatory or important attributes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety needs no restating. The description adds value by disclosing the shape of the returned data (attributeId, allowedValues[].key, filterability/exposability), which matters because no output schema exists.

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?

Two sentences, zero filler, purpose front-loaded and the follow-up routing instruction second. Nothing could be cut without losing information.

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?

With no output schema, the description carries the burden of describing returns and does so partially by naming attributeId and allowedValues[].key. It doesn't mention other likely returned fields (attribute names/labels, importance flags) or confirm that results are unfiltered by default, but it is sufficient to call correctly.

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 categoryId, searchQuery, and onlyImportant are already fully documented. The description only echoes the categoryId notion and says nothing about the searchQuery name-filter or the onlyImportant flag, so it adds little beyond the schema baseline.

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 (retrieve) and resource (filterable/exposable attributes plus allowed option keys) scoped to a categoryId, with concrete examples (Condition, Brand, Storage, Material). It also names the downstream sibling aukro_search_offers, so an agent can place it in the workflow without opening other schemas.

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 second sentence gives clear downstream usage: feed attributeId and allowedValues[].key into aukro_search_offers's attributeFilters. What's missing is the upstream dependency (categoryId comes from aukro_get_categories) and any explicit exclusion, such as when aukro_autocomplete is preferable.

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