Skip to main content
Glama
Sign In
MisarBlog MCP Server

MisarBlog MCP Server

by Misar-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search articles

search_articles
Read-onlyIdempotent

Find published articles on Misar.Blog by keyword, tag, or author, including other creators' work. Use it to locate public posts, not your own drafts.

Instructions

Search PUBLISHED articles across Misar.Blog by keyword, tag, or author — including other creators' work. Use list_my_articles for your own drafts and unpublished posts.

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": "search_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoKeyword query (min 2 characters)
tagNoFilter by tag
limitNoResults to return (1-20)
authorNoFilter by author username

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed4 schema fields changedv5.1.3
    • changedInput schema / properties / author / description
      Previous value: -"Restrict to one author, by username."New value: +"Filter by author username"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results to return, 1-20. Defaults to 10."New value: +"Results to return (1-20)"
    • changedInput schema / properties / q / description
      Previous value: -"Free-text query matched against title and body. Minimum 2 characters."New value: +"Keyword query (min 2 characters)"
    • changedInput schema / properties / tag / description
      Previous value: -"Restrict to articles carrying this exact tag."New value: +"Filter by tag"
  3. Changed4 schema fields changedv5.1.0
    • 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."
  4. First observedv2.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds behavior-relevant context beyond that: results are restricted to published articles and reach beyond the caller's own content. It does not mention result ordering, pagination, or what a hit contains, which keeps it short of a 5.

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 with zero filler. The positive scope leads and the disambiguation clause follows, which is the right front-loading for a routing-sensitive tool.

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 search with four fully documented optional parameters and no output schema, the description supplies what an agent needs to choose the tool and pick facets. The remaining gap is filter-combination semantics and result paging, which are unaddressed but modest for this complexity.

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 coverage is 100% with min/max bounds and defaults documented, so the baseline is 3. The description names the three filter facets but adds no meaning on how they combine (AND vs OR) or whether q is required alongside tag/author, so it does not exceed the schema.

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 and resource ("Search PUBLISHED articles across Misar.Blog") plus the supported facets (keyword, tag, author) and the crucial scope note that other creators' work is included. An agent can distinguish this from list_my_articles without opening 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 alternative sibling (list_my_articles) and the condition that selects it: your own drafts and unpublished posts. The inverse condition — this tool for published, including others' work — is stated in the same breath, so the routing decision is fully determined.

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