mcp-server

Subscribe to Programme-Change Alerts

subscribe_changes

Subscribe to verified programme-change alerts (price changes, launches, corrections — each linked to the official source). Agents: provide webhook_url (HTTPS POST on each change). Humans: provide email (explicit consent required). Optional programme_ids filter. Returns a subscription id + unsubscribe URL.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	No	email for change alerts (requires consent:true)
`consent`	No	required true when email is given (GDPR)
`website`	No	leave blank (spam honeypot)
`webhook_url`	No	HTTPS endpoint to POST change entries to (for agents/systems)
`programme_ids`	No	optional filter — only these programmes

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only when the request could not be fulfilled.
`terms`	No	Acceptable-use and information-not-advice terms.
`source`	No	Attribution for the data.
`provider`	No	Always "Mirabello Consultancy".
`disclaimer`	No	Information, not legal/tax/financial/immigration advice; figures indicative.
`data_updated`	No	Date the underlying dataset was last updated.
`book_a_consultation`	No	URL to book a Mirabello consultation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Mirabello response envelope. Tool-specific fields vary; the provenance/disclaimer envelope is always present.",
+  "properties": {
+    "book_a_consultation": {
+      "description": "URL to book a Mirabello consultation.",
+      "type": "string"
+    },
+    "data_updated": {
+      "description": "Date the underlying dataset was last updated.",
+      "type": "string"
+    },
+    "disclaimer": {
+      "description": "Information, not legal/tax/financial/immigration advice; figures indicative.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Present only when the request could not be fulfilled.",
+      "type": "string"
+    },
+    "provider": {
+      "description": "Always \"Mirabello Consultancy\".",
+      "type": "string"
+    },
+    "source": {
+      "description": "Attribution for the data.",
+      "type": "string"
+    },
+    "terms": {
+      "description": "Acceptable-use and information-not-advice terms.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, and the description adds valuable behavioral context: webhook_url will receive an HTTPS POST on each change, email requires explicit consent, and the call returns a subscription id plus unsubscribe URL. This clarifies the ongoing side-effect nature of the subscription beyond what annotations alone convey.

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 three sentences with no filler. It front-loads the purpose, then gives the channel-specific usage, the optional filter, and the return value. Every sentence contributes to successful invocation.

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?

Given the output schema exists and the parameters are fully described in the schema, the description provides the missing operational context: when to choose email vs webhook, that consent is required for email, the optional filter, and the subscription artifact returned. An agent has enough information to invoke this tool correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds some selection guidance (agents use webhook_url, humans use email, programme_ids is optional), but most of this is already present in the schema descriptions. It does not introduce significant new meaning for individual 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 and resource: 'Subscribe to verified programme-change alerts', and details what kinds of changes are included (price changes, launches, corrections) with a link to official sources. This distinguishes it clearly from sibling tools like get_recent_changes, which focus on retrieving current changes rather than creating ongoing subscriptions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage context by dividing the audience: agents should provide webhook_url, humans should provide email with explicit consent, and programme_ids is an optional filter. It does not explicitly name alternatives or state when not to use this tool, but the subscription-focused phrasing makes the intended scenario evident.

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

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.