Skip to main content
Glama
Sign In
asalbanoo-mcp

asalbanoo-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Current deals

ab_deals
Read-onlyIdempotent

List discounted in-stock cosmetics and personal care products, ranked by biggest discount first, with an optional category filter and a limit on results.

Instructions

List discounted in-stock products, biggest discount first.

Use for "what's on sale" / "discounted sunscreens"; optionally one category slug from ab_categories. Ranks the first 300 deals: complete=false means more exist (see total).

Input Schema

NameRequiredDescriptionDefault
limitNoMax deals to return.
categoryNoCategory slug from ab_categories, e.g. 'hair-shampoo' or 'sunscreen'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • removedInput schema / properties / category / title
      Removed value: -"Category"
    • changedInput schema / properties / limit / default
      Previous value: -30New value: +20
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / title
      Removed value: -"ab_dealsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ab_dealsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's value-add is the truncation behavior: ranking is limited to the first 300 deals and complete=false signals more exist, with total available. That is genuinely useful non-obvious behavior beyond the annotations.

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?

Three tight clauses: what it lists and how it ranks, when to use it, and the pagination caveat. Leading sentence front-loads the essential behavior with zero filler.

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?

With no output schema, the description responsibly surfaces the one return-value detail an agent needs (complete flag and total) that would otherwise be invisible. Filtering, ranking, and result-size behavior are all covered for a simple two-parameter read 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 description coverage is 100% and the schema already documents both parameters, including the category slug source (ab_categories) and the example slugs plus the limit bound. The description's category guidance therefore largely repeats structured data rather than adding new semantics.

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 (List), resource (discounted in-stock products) and scope/ordering (biggest discount first), which separates it from siblings like ab_find_cheapest (cheapest) and ab_search (general query). An agent can pick this tool without opening the schema.

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?

Gives concrete user-intent triggers ("what's on sale" / "discounted sunscreens") and notes the category filter is optional and single-valued. It does not explicitly name a competing sibling or state when NOT to use it, which keeps it 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