Skip to main content
Glama
sepehr071

asalbanoo-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List categories

ab_categories
Read-onlyIdempotent

List product categories with slugs and counts to find the category slug needed for browsing or filtering products; optionally filter by Persian name or slug.

Instructions

List product categories (about 70) with slugs and counts.

Use to get a category slug for ab_browse / ab_filters. parent = parent category id (0 = top level); count includes out-of-stock products.

Input Schema

NameRequiredDescriptionDefault
queryNoOptional filter on the Persian name or slug, e.g. 'شامپو' or 'sun'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"ab_categoriesArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ab_categoriesDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful data semantics the annotations cannot convey: the list is ~70 entries and the count includes out-of-stock products. No pagination or ordering note, but the set is small enough that this matters little.

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 core sentence is front-loaded and dense with useful facts (verb, resource, scale, return fields), and the routing sentence follows immediately. The trailing 'parent'/count line is partially wasted because 'parent' maps to nothing in the schema, costing it a point.

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?

For a single-parameter, read-only listing tool with no output schema and rich annotations, the description covers scope, purpose, return fields, and routing to consumers. The only blemish is the orphaned 'parent' reference, which is a minor documentation inconsistency rather than a missing capability.

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% for the single 'query' parameter, so the baseline is 3. The description's parameter line instead describes 'parent = parent category id (0 = top level)', a parameter that does not exist in the schema, which is stale or mismatched text rather than added meaning; the 'count includes out-of-stock' note is the only real semantic addition.

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 and resource with useful scope: 'List product categories (about 70) with slugs and counts.' The cardinality and the returned fields (slugs, counts) tell an agent exactly what it gets. It does not directly contrast itself with the close peer ab_brands, so differentiation is implied rather than stated.

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?

'Use to get a category slug for ab_browse / ab_filters' names the downstream tools and the reason to call this one, which is real routing guidance. It omits any when-not condition (e.g. when ab_brands or ab_search is the better choice), so it falls short of full alternative coverage.

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

Deploy Server

Other Tools