Skip to main content
Glama

Misar.Blog MCP Server

by io.github.Misar-AI

Search published articles

search_articles
Read-onlyIdempotent

Search PUBLISHED articles across all of Misar.Blog, including other creators' work.

Use this for discovery, research, and competitive reading. It never returns drafts, scheduled, or private posts — not even your own — so reach for list_my_articles when you want your unpublished work.

Reads only. No API key required; unauthenticated callers are rate-limited by IP. Filters combine with AND. Returns an array of article summaries without bodies; pass a slug to get_article for the full text. An empty array means no matches, which is not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text query matched against title and body. Minimum 2 characters.
tagNoRestrict to articles carrying this exact tag.
limitNoMaximum results to return, 1-20. Defaults to 10.
authorNoRestrict to one author, by username.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • changedInput schema / properties / author / description
      Previous value: -"Filter by author username"New value: +"Restrict to one author, by username."
    • changedInput schema / properties / limit / description
      Previous value: -"Results to return (1-20)"New value: +"Maximum results to return, 1-20. Defaults to 10."
    • changedInput schema / properties / q / description
      Previous value: -"Keyword query (min 2 characters)"New value: +"Free-text query matched against title and body. Minimum 2 characters."
    • changedInput schema / properties / tag / description
      Previous value: -"Filter by tag"New value: +"Restrict to articles carrying this exact tag."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description adds meaningful behavioral details: unauthenticated callers are rate-limited by IP, filters combine with AND, results are summaries without bodies, and an empty array indicates no matches rather than an error. These are not implied by readOnlyHint or openWorldHint and are valuable for correct agent behavior.

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?

The description is compact, well-structured, and front-loaded with the core purpose. Every sentence contributes either scope clarification, usage guidance, behavioral context, or return-value semantics, with no filler or repetition.

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?

Given four optional parameters, no output schema, and important edge behavior (draft visibility, rate limits, empty results), the description covers the necessary ground: what is searched, what is excluded, how to retrieve full content, filter combination, and error semantics. This is sufficient for confident tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already covers 100% of parameters with useful descriptions, so the baseline is 3. The description adds the cross-cutting semantic that 'Filters combine with AND,' which is not stated in the individual schema fields and clarifies how to compose multiple parameters.

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?

The description opens with a specific verb and resource: 'Search PUBLISHED articles across all of Misar.Blog, including other creators' work.' It clearly distinguishes this discovery-oriented search from list_my_articles, which returns the caller's unpublished work, and from get_article, which returns full article text.

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?

The description explicitly states when to use the tool ('discovery, research, and competitive reading') and names the alternative for unpublished content ('reach for list_my_articles when you want your unpublished work'). It also directs the agent to get_article for full-text needs, making the decision boundary very clear.

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

All Misar.Blog MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Tools have clear, distinct purposes. Even similar tools like generate_title_seo and suggest_titles are clearly separated by input type (topic vs draft). The descriptions are exhaustive, preventing confusion.

Naming Consistency5/5

All tools use lowercase snake_case with verb-first naming. Slight inconsistency: 'upgrade' is a bare verb while others are verb_noun, but overall pattern is consistent.

Tool Count4/5

23 tools is a large but justifiable set for a full-featured blogging platform covering articles, series, reactions, newsletter, analytics, and AI assistance. It borders on the high end but remains scoped.

Completeness2/5

The tool set covers creation, publishing, updating, and listing of articles, but lacks delete operations for articles and series, and offers no comment management beyond reading. This leaves notable lifecycle gaps.

Resources