Skip to main content
Glama
Misar-AI

MisarBlog MCP Server

by Misar-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Plan usage and upgrade

upgrade
Idempotent

Check your Misar.Blog plan, remaining quotas, and what higher tiers unlock; get the plan-change link or start a free no-card trial if eligible.

Instructions

Show your current Misar.Blog plan, how much of each quota you have left, and what upgrading unlocks, with the link to upgrade. Call it any time — not only after hitting a limit. By default it only reads. With start_trial=true it starts the free, no-card trial on the account (a plan change; no payment is taken). It never upgrades a paid plan or takes payment itself: the user does that by following the link. On a local install, open=true also opens that link in the user's browser.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
openNoLocal installs only: also open the upgrade link in the user's browser. Ignored by the hosted server, which returns the link instead.
planNoPlan slug to open (e.g. 'pro', 'business'). Defaults to the recommended plan.
start_trialNoStart the free no-card trial immediately, if you're eligible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv5.1.3
    • changedInput schema / properties / open / description
      Previous value: -"Open the checkout page in the user's default browser. Side effect on their desktop — only when they asked to upgrade."New value: +"Local installs only: also open the upgrade link in the user's browser. Ignored by the hosted server, which returns the link instead."
    • changedInput schema / properties / plan / description
      Previous value: -"Plan slug to open, e.g. 'pro' or 'business'. Defaults to the recommended plan. Only meaningful with open=true."New value: +"Plan slug to open (e.g. 'pro', 'business'). Defaults to the recommended plan."
    • changedInput schema / properties / start_trial / description
      Previous value: -"Enrol in the free no-card trial now, if eligible. This changes the account's plan — do not set it speculatively."New value: +"Start the free no-card trial immediately, if you're eligible."
  2. Changed3 schema fields changedv5.1.0
    • 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."
  3. First observedv2.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false with a mutating path, and the description explains exactly that: read-only by default, a plan change only with start_trial, and no payment ever taken. It also discloses the local-install browser side effect, adding context 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?

Front-loaded with what the tool shows, then the behavioral caveats, with no filler. Slightly repetitive in restating that the user follows the link to pay, but it is tight overall.

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 3-optional-param tool with no output schema, the description covers default behavior, the mutating branch, payment safety, and the local-install variant, so an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema doesn't carry: start_trial is a plan change that takes no payment, and open is a local-only branch that the hosted server ignores in favor of returning the link.

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 uses a concrete verb set (show plan, remaining quota, unlocked features, upgrade link) rather than restating the name. It is clearly distinguishable from every sibling, none of which touch billing or plan state.

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 explicitly tells the agent to call it any time, not just after a limit, and spells out the exact conditions that change behavior: start_trial=true starts a trial, while open=true matters only on local installs. It also states what the tool will not do (upgrade a paid plan, take payment), which is precise routing guidance.

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