Website Auditor MCP

Check upgrade status

check_upgrade_status

Read-only

Check your Website Auditor subscription status: see if you're on Free or Pro, trial end, cancellation, and upgrade details. Use when a feature is locked or before upgrading.

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.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context beyond annotations: it targets the caller's own subscription, works with any valid key, consumes no audit quota, and details the exact return fields including a plain-language summary and Pro requirements. This gives the agent a clear model of what calling the tool will do and what it won't do.

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 well-structured: it opens with the core purpose, follows with explicit usage triggers, then covers behavior and return values in one efficient list. Every sentence adds useful information, and the trigger phrases are front-loaded for quick comprehension.

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 subscription status tool, the description is complete. It covers purpose, applicable triggers, side-effect-free behavior, and what the caller receives in the response. The output schema exists, but the description still usefully summarizes the meaningful return fields without being redundant.

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 has zero parameters, so the baseline is 4. The description still clarifies that the tool inherently operates on 'the caller's own' subscription, which is meaningful contextual semantics even without input parameters.

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 states a specific verb ('Check') and a precise resource: the caller's own Website Auditor subscription standing. It clearly distinguishes this from sibling tools by naming the exact user questions it answers ('am I on Pro,' 'is my trial still active'), so the agent can select it unambiguously.

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?

The description gives explicit when-to-use guidance with concrete trigger phrases and even 'before suggesting an upgrade.' It also clarifies that it 'Works with any valid API key and consumes no audit quota,' which helps the agent decide whether this tool is appropriate in edge cases like locked tools or trial inquiries.

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

Deploy Server