Skip to main content
Glama
asalbanoo-mcp

asalbanoo-mcp

by sepehr071

Blog posts and care guides

ab_blog_posts
Read-onlyIdempotent

List and search Asal Banoo skin and hair care blog posts, newest first, to find relevant advice guides or comparisons before opening a post for details.

Instructions

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

Use for advice questions: find a post, then read it with ab_blog_post.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ab_blog_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoFrom 1.
limitNoPosts per page.
queryNoKeyword, e.g. 'ضد آفتاب'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • changedInput schema / properties / page / description
      Previous value: -"Page number, from 1, newest first."New value: +"From 1."
    • changedInput schema / properties / query / description
      Previous value: -"Optional keyword, e.g. 'ضد آفتاب' or 'پوست چرب'."New value: +"Keyword, e.g. 'ضد آفتاب'."
  2. 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
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the one behavioral fact annotations cannot convey: results are returned newest first, which matters for how an agent interprets the first page. It does not mention pagination behavior or total counts, keeping it just below the top mark.

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, both front-loaded: the scope and ordering come first, the usage routing second. There is no filler, and every clause (content types, ordering, follow-up tool) carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description never says what a list entry contains — notably whether it returns the identifier or slug needed to call ab_blog_post, which is the very next step it recommends. The core call is understandable, but the handoff to the detail tool is left for the agent to discover.

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%, so page, limit and query are already documented with defaults and bounds, and the description adds nothing beyond that. It never explains how the query keyword is matched (title vs body, Persian-language examples) or that omitting it returns the full list, so the baseline 3 applies.

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?

The description gives a concrete verb and resource ("List Asal Banoo blog posts") and even characterizes the content types (care guides, routines, "X vs Y" comparisons) plus the default ordering (newest first). It implicitly separates itself from the sibling ab_blog_post by pointing to that tool for reading a single post, though it never contrasts itself with ab_search, which could plausibly return similar content.

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 for advice questions: find a post, then read it with ab_blog_post" states the triggering scenario and the correct two-step workflow with the exact follow-up sibling. It stops short of exclusions — nothing says to use ab_product or ab_search instead when the question is about a product rather than advice.

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