Skip to main content
Glama
sepehr071

masterkala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Blog post comments

mk_blog_comments
Read-only

Read blog post comments as threads, including MasterKala's replies, to surface reader product questions and answers as a support FAQ.

Instructions

Read the comments of a blog post as threads, with the store writer's answers as replies.

Useful as a support FAQ: many posts hold readers' product questions answered by MasterKala.

Input Schema

NameRequiredDescriptionDefault
limitNoMax comment threads to return, newest first.
post_idYesBlog post id from mk_blog_posts, e.g. 330.
full_textNoReturn comment text uncut and all replies (default: 400 chars, 3 replies).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "Return comment text uncut and all replies (default: 400 chars, 3 replies).",
+  "type": "boolean"
+}
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / post_id / title
      Removed value: -"Post Id"
    • removedInput schema / title
      Removed value: -"mk_blog_commentsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mk_blog_commentsDictOutput",
-  "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?

readOnlyHint=true already establishes the safe-read profile, so the description only needs to add context. It contributes the thread/reply grouping model, but the truncation behavior (400 chars, 3 replies) and the full_text escape hatch live only in the schema. Modest value added beyond 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?

Two short sentences, zero filler, with the core behavior front-loaded and the use-case context second. 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?

No output schema exists, but the description communicates the return shape (threads with replies) and the read-only nature is covered by annotations. An agent has enough to call it correctly; only the response envelope details remain unstated.

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 limit, post_id and full_text are fully documented in-schema including the truncation defaults. The description adds no parameter syntax or format detail beyond that, making the baseline 3 correct.

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 and resource – reading a blog post's comments as threads with writer replies. Clearly separable from mk_blog_posts (which supplies the post_id) and from other mk_* tools. Lacks an explicit sibling comparison, but the resource distinction is unambiguous.

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?

"Useful as a support FAQ: many posts hold readers' product questions answered by MasterKala" gives a concrete scenario for when an agent should reach for this tool. No exclusions or named alternatives are provided, 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