Skip to main content
Glama
sepehr071

asalbanoo-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Read a blog post

ab_blog_post
Read-onlyIdempotent

Read one blog post as plain text with its linked products and categories, helping agents answer care questions from shop guides.

Instructions

Read one blog post as plain text, plus the products and categories it links to.

Use after ab_blog_posts to answer care questions from the shop's own guides. Linked products can be looked up with ab_search (by name) and categories browsed with ab_browse (slug).

Input Schema

NameRequiredDescriptionDefault
post_idYesPost id from ab_blog_posts, e.g. 791485.
max_charsNoCut the text after this many characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • removedInput schema / properties / max_chars / title
      Removed value: -"Max Chars"
    • removedInput schema / properties / post_id / title
      Removed value: -"Post Id"
    • removedInput schema / title
      Removed value: -"ab_blog_postArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ab_blog_postDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and idempotency are covered. The description adds that output is plain text with linked products/categories, which is meaningful behavioral context. However with no output schema, more detail on return structure and the truncation behavior would help.

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 plus a routing sentence, front-loaded with the core operation. Every clause earns its place by pointing to the source tool and follow-up tools.

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 2-param read tool with full schema coverage and rich annotations, the description covers purpose, sequencing, and how to use the linked data. It does not explain the maximum text length or truncation behavior beyond the schema, but the overall picture is complete enough to invoke correctly.

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 both post_id (source and example) and max_chars (truncation semantics, default and range) are fully documented in the schema. The description adds no format or syntax detail beyond what the schema provides, so baseline 3 is appropriate.

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 (read) and resource (one blog post), plus its scope: plain text with linked products and categories. It also references the sibling ab_blog_posts as the source of post ids. It is clear, though it doesn't explicitly contrast against other read tools like ab_product.

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 the sequencing context: use after ab_blog_posts to answer care questions. It names the right follow-up tools for the linked data (ab_search by name, ab_browse by slug). No explicit when-not-to-use is given, but the workflow guidance is concrete and useful.

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