Skip to main content
Glama
sepehr071

asalbanoo-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List brands

ab_brands
Read-onlyIdempotent

List about 250 brands with slugs and product counts, biggest first. Get the correct brand slug for ab_browse or ab_filters before querying products.

Instructions

List brands (about 250) with slugs and product counts, biggest first.

Use to get the brand slug for ab_browse / ab_filters. The Latin slug usually matches better than Persian spellings ('vichy', 'la-roche-posay').

Input Schema

NameRequiredDescriptionDefault
limitNoMax brands, biggest first.
queryNoOptional filter on the Persian name or Latin slug, e.g. 'graph' or 'ویشی'.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond them: the ~250 total size, the biggest-first ordering, and the recommendation to match on Latin slugs rather than Persian spellings.

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 short sentences, front-loaded with what the tool returns and what it is for; every clause carries information and nothing is padded.

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 still names the returned fields (slug, product count) and the ordering, and the limit/query behavior lives in a fully documented schema. It stops short of describing pagination or whether the ~250 total is ever truncated by limit.

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 coverage is 100%, so the baseline is 3, but the note that the Latin slug usually matches better than Persian spellings directly improves how the optional `query` filter should be constructed, beyond the schema's own examples.

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 ('List brands') and immediately qualifies the result set: ~250 entries, returned with slugs and product counts, ordered biggest first. An agent knows exactly what it gets and how it differs from a generic listing.

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?

Explicitly routes the agent: 'Use to get the brand slug for ab_browse / ab_filters', which names the downstream siblings that consume this output. No when-not guidance (e.g. when ab_categories would be the better list tool), so it falls short of a 5.

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