Website Auditor MCP

Check upgrade status

check_upgrade_status

Read-only

Check your Website Auditor subscription status to see your tier, trial status, renewal date, and upgrade requirements without using audit quota.

Instructions

Check the caller's own Website Auditor subscription standing. Use this when someone asks "am I on Pro," "is my trial still active," "when does my subscription renew/end," "why is this tool locked," or before suggesting an upgrade. Works with any valid API key and consumes no audit quota. Returns the tier (none/free/pro), raw subscription status, period end, whether the subscription is set to cancel, the upgrade URL, and a plain-language summary — including what starting Pro requires (a payment method and accepting the Terms).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`tier`	Yes	"none" \| "free" \| "pro".
`status`	Yes	Raw subscription status: active, trialing, canceled, none, …
`message`	Yes
`upgrade_url`	Yes
`current_period_end`	Yes
`cancel_at_period_end`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.23Sep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "cancel_at_period_end": {
+      "type": "boolean"
+    },
+    "current_period_end": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "status": {
+      "description": "Raw subscription status: active, trialing, canceled, none, …",
+      "type": "string"
+    },
+    "tier": {
+      "description": "\"none\" | \"free\" | \"pro\".",
+      "type": "string"
+    },
+    "upgrade_url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "tier",
+    "status",
+    "current_period_end",
+    "cancel_at_period_end",
+    "upgrade_url",
+    "message"
+  ],
+  "type": "object"
+}

First observedv1.0.6Jul 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond them: no audit quota is consumed and any valid API key works, which the agent cannot infer from annotations. Most of the remaining text enumerates return fields that the output schema already carries, so this is strong but not maximal.

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 purpose then triggers, and every clause is actionable. The lengthy enumeration of return fields (tier, raw status, period end, cancel flag, upgrade URL, summary) partly duplicates the output schema, which is the one place the text does not fully earn its length.

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 zero-parameter, read-only status tool with an output schema, the description covers everything an agent needs: when to call it, auth requirements, quota cost, and what starting Pro requires. Nothing essential is missing.

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?

The tool takes zero parameters, so schema coverage is moot and the baseline of 4 applies. The description usefully implies there is no subject argument — it only reports the caller's own subscription — which prevents an agent from hunting for a user ID to pass.

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 — 'Check the caller's own Website Auditor subscription standing' — and the 'caller's own' scope cleanly separates it from every sibling, none of which touch subscription state. An agent can identify the tool from the first sentence alone.

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?

Gives explicit trigger conditions with quoted user phrasing ('am I on Pro', 'is my trial still active', 'why is this tool locked') plus a proactive case ('before suggesting an upgrade'). It also names the precondition for use (any valid API key) and confirms no cost, so an agent knows both when and how freely to call it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server