Skip to main content
Glama
sepehr071

asalbanoo-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Blog posts and care guides

ab_blog_posts
Read-onlyIdempotent

Search Asal Banoo skin and hair care posts, newest first, to match advice questions; then read a post for guides, routines, and comparisons.

Instructions

List Asal Banoo blog posts (skin and hair care guides, routines, "X vs Y" comparisons), newest first.

Use for advice questions ("best moisturizer for oily skin", "Vichy or Clinique?"): find a matching post, then read it with ab_blog_post.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1, newest first.
limitNoPosts per page.
queryNoOptional keyword, e.g. 'ضد آفتاب' or 'پوست چرب'.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world behavior, so the safety profile is covered. The description adds the newest-first ordering and the list-then-read pattern, which is useful, but says nothing about pagination limits (100 pages, 30 max per page) or the shape of returned post objects. With annotations carrying the safety burden, a 3 is appropriate.

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 tight sentences with zero filler: the first defines the resource and ordering, the second defines when to use it and the follow-up tool. Front-loaded and every clause earns its place.

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?

For a read-only list tool with full schema coverage and rich annotations, the description covers purpose, ordering, and the list-then-read workflow. It does not describe return payload or pagination behavior, but no output schema exists and those gaps are minor here.

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 page, limit, and query with constraints and an example. The description mentions 'newest first' which reinforces the ordering of page, but adds no further syntax or format detail. Baseline 3 when the schema does the heavy lifting.

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) and resource (Asal Banoo blog posts), enumerates the content types covered (care guides, routines, comparisons), and specifies ordering (newest first). An agent can distinguish this listing tool from the singular ab_blog_post reader without inspecting either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the use case (advice questions), gives concrete example queries, and prescribes a two-step workflow: find a matching post here, then read it with ab_blog_post. That routing between the sibling tools is exactly what an agent needs.

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