Skip to main content
Glama

Misar.Blog MCP Server

by blog.misar

Show plan and quota, or upgrade

upgrade
Idempotent

Show the account's current plan, how much of each quota remains, and what a higher plan unlocks.

Called with no arguments it only reads — useful any time, not just after hitting a limit, and the natural follow-up when a write tool reports a quota error. Two arguments make it act rather than report, so pass them only on explicit instruction from the user: start_trial ENROLS the account in the free trial immediately (a real account change, not a preview), and open LAUNCHES a checkout page in the user's browser. Neither charges a card by itself.

Requires an API key. No billing state changes unless you pass start_trial; the returned quota snapshot already reflects a trial started in the same call. For whether you are authenticated at all, use status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
openNoOpen the checkout page in the user's default browser. Side effect on their desktop — only when they asked to upgrade.
planNoPlan slug to open, e.g. 'pro' or 'business'. Defaults to the recommended plan. Only meaningful with open=true.
start_trialNoEnrol in the free no-card trial now, if eligible. This changes the account's plan — do not set it speculatively.

TDQS

A4.9/5.0
Behavior5/5

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

Discloses that start_trial changes the account plan, open launches a checkout page, and neither charges a card. Also notes that no billing changes occur unless start_trial is passed, and mentions API key requirement. Adds specificity beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat lengthy but well-structured in three paragraphs, each addressing a distinct aspect (purpose, usage, side effects). No redundancy, but could be slightly more concise.

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?

Covers all necessary context: when to use, side effects, required authentication, and no output schema needed. No gaps detected.

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

Parameters5/5

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

Each parameter (open, plan, start_trial) is explained in the description with side effects and defaults. The input schema descriptions are reinforced, and additional behavioral context is provided (e.g., 'real account change').

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 dual purpose: showing plan/quota and performing upgrades when specific arguments are provided. It distinguishes from sibling tools focused on content creation or management.

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 explains when to use the read-only mode (anytime) and when to use the action mode (only on explicit user instruction). Provides context as a natural follow-up after quota errors, and warns against unsolicited use of start_trial and open.

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