Skip to main content
Glama

Misar.Blog MCP Server

by blog.misar

Create a series

create_series

Create a new, empty series — a named collection that related articles can be added to.

Creating the series does not move any article into it; follow up with add_to_series for each one. Call get_series first to avoid making a second series with the same title, since each call creates a NEW series and nothing deduplicates them.

Requires an API key. The series and its URL become publicly reachable, though it shows nothing until articles are added. Returns the series with the slug that add_to_series needs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesDisplay name of the series. The slug is derived from this.
descriptionNoShort summary shown on the series page. Optional.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare it as write, non-idempotent, and non-destructive. The description adds valuable behavioral details: API key requirement, public reachability, lack of deduplication, and the output containing a slug. These go beyond the annotations and do not contradict them.

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 tightly written with no fluff. Each sentence adds essential information: purpose, usage sequence, dedup warning, API key, public visibility, and output. It is well-structured and front-loads the primary purpose.

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?

For a simple creation tool with no output schema, the description covers all necessary aspects: what it does, prerequisites, side effects, and return value. It compensates for the missing output schema by explicitly stating the slug is returned for add_to_series.

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% and both parameters are already described (title with slug derivation, optional description). The description adds no extra parameter-specific semantics beyond what the schema provides, so it meets the baseline but doesn't enhance it.

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 clearly states the tool creates a new, empty series and distinguishes it from related operations like add_to_series and get_series. It explicitly notes that it does not move articles, which uniquely identifies its scope among siblings.

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?

Provides explicit usage context: call get_series first to avoid duplicates, follow up with add_to_series for each article, and requires an API key. It also mentions the returned slug is needed for add_to_series, effectively guiding the agent through the correct workflow.

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.1/5.0
Disambiguation4/5

The tools mostly map to clearly distinct resources and actions, with good behavioral separation between create_draft, publish_article, and update_article, and between the two title-generating tools. Some naming choices are still slightly misleading, such as get_series returning the full collection rather than a single series, and generate_cover_image references a non-existent upload_image tool.

Naming Consistency4/5

The vast majority of tools follow a clean lowercase verb_noun pattern, including create_*, get_*, list_*, and add_* names. Notable exceptions are upgrade, a bare verb that also mixes read and mutate behaviors, and get_series, which functions more like a list than a get.

Tool Count3/5

23 tools is in the heavy range for an MCP server, exceeding the ideal 3-15 span. That said, the tools do span legitimate blogging concerns such as articles, reactions, series, newsletters, analytics, and AI assistance, so the count feels broad rather than padded.

Completeness2/5

The surface covers article creation, reading, updating, and publishing, but there is no delete or unpublish for articles/drafts, no way to remove an article from a series, and no update/delete for series. The dangling reference to upload_image in generate_cover_image also suggests a missing tool, and agents will hit dead ends trying to undo publication or remove content.

Resources