Skip to main content
Glama

Misar.Blog MCP Server

by io.github.Misar-AI

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.

Schema Changelog

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

  1. Changed3 schema fields changed
    • changedInput schema / properties / open / description
      Previous value: -"Open the upgrade/checkout page in the default browser."New value: +"Open the checkout page in the user's default browser. Side effect on their desktop — only when they asked to upgrade."
    • changedInput schema / properties / plan / description
      Previous value: -"Plan slug to open (e.g. 'pro', 'business'). Defaults to the recommended plan."New value: +"Plan slug to open, e.g. 'pro' or 'business'. Defaults to the recommended plan. Only meaningful with open=true."
    • changedInput schema / properties / start_trial / description
      Previous value: -"Start the free no-card trial immediately, if you're eligible."New value: +"Enrol in the free no-card trial now, if eligible. This changes the account's plan — do not set it speculatively."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description clarifies that no-arg calls are read-only, while with arguments it can change the account (start trial) or open a browser (checkout). It adds that neither action charges a card, and notes the API key requirement, all beyond the annotations which only indicate not read-only and idempotent.

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 structured in three sentences, front-loaded with the primary purpose and follow-up details. It is slightly verbose with repeated emphasis on 'only on explicit instruction', but remains clear and not overly long.

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?

The description fully covers the tool's dual nature (read vs. act), when to use it, side effects (trial/checkout), and dependencies. It also provides the API key requirement and cross-references the `status` tool, making it complete for practical use.

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?

The schema already provides descriptions for all three parameters, including the dependency between `plan` and `open`. The description text does not add substantial information beyond the schema, so it remains at the baseline for high coverage.

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 explicitly states the tool shows the account's plan and quota, and optionally upgrades via trial or checkout. It distinguishes from sibling tools (which are article/title related) by focusing on account billing and plan 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?

It clearly says the tool is useful for checking quota anytime and as a follow-up after quota errors, and explicitly instructs to use `start_trial` and `open` only on explicit user instruction. It also points to the `status` tool for authentication, providing an alternative.

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