Skip to main content
Glama
Sign In

Advocate

by com.advocatemcp
OverviewDiscussionsAdmin

Subscribe to Updates

subscribe_to_updates
DestructiveIdempotent

Start a pending email subscription to updates from a business. Returns a confirmation URL that only the user must click within 7 days; no subscription is active until that confirmation. Idempotent: re-using the same idempotency_key returns the original subscription.

Input Schema

NameRequiredDescriptionDefault
slugYesBusiness slug identifier
topicsYesTopic tags (e.g., ['deals', 'schedule_changes'])
agent_idNoOptional agent identifier
contact_emailYesEmail to subscribe — confirmed via returned token
idempotency_keyYesIdempotency key

Output Schema

NameRequiredDescriptionDefault
statusYes'pending' until the user opens confirmation_url; a replay returns the stored state (e.g. 'confirmed' once they have)
topicsYesNormalised topic tags: trimmed, lower-cased, de-duplicated
expires_atYesUnix seconds when confirmation_url stops working
acknowledgmentYesCustomer-facing sentence to relay, including the confirmation link
subscription_idYes
confirmation_urlYesThe link the user must open within 7 days to start receiving updates
idempotent_replayNoPresent and true when this idempotency_key already had a subscription; the stored token is returned, refreshed only if it had expired
confirmation_tokenYesCapability token for this subscriber only — it is the proof of consent; never pass it to another tool or party

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / contact_email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    • removedOutput schema / properties / acknowledgment / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / acknowledgment / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / status / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / status / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "acknowledgment": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Customer-facing sentence to relay, including the confirmation link"
+    },
+    "confirmation_token": {
+      "description": "Capability token for this subscriber only — it is the proof of consent; never pass it to another tool or party",
+      "type": "string"
+    },
+    "confirmation_url": {
+      "description": "The link the user must open within 7 days to start receiving updates",
+      "type": "string"
+    },
+    "expires_at": {
+      "description": "Unix seconds when confirmation_url stops working",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "idempotent_replay": {
+      "description": "Present and true when this idempotency_key already had a subscription; the stored token is returned, refreshed only if it had expired",
+      "type": "boolean"
+    },
+    "status": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "'pending' until the user opens confirmation_url; a replay returns the stored state (e.g. 'confirmed' once they have)"
+    },
+    "subscription_id": {
+      "format": "uuid",
+      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+      "type": "string"
+    },
+    "topics": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Normalised topic tags: trimmed, lower-cased, de-duplicated"
+    }
+  },
+  "required": [
+    "subscription_id",
+    "status",
+    "confirmation_token",
+    "confirmation_url",
+    "expires_at",
+    "topics",
+    "acknowledgment"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / contact_email / format
      Added value: +"email"
    • addedInput schema / properties / contact_email / pattern
      Added value: +"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  4. Changed9 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / agent_id / description
      Previous value: -"Optional caller-asserted agent identifier; recorded for attribution"New value: +"Optional agent identifier"
    • changedInput schema / properties / contact_email / description
      Previous value: -"Email to subscribe — must be confirmed via the returned token before any updates send"New value: +"Email to subscribe — confirmed via returned token"
    • removedInput schema / properties / contact_email / format
      Removed value: -"email"
    • addedInput schema / properties / contact_email / minLength
      Added value: +1
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Idempotency key",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / slug / description
      Previous value: -"business slug"New value: +"Business slug identifier"
    • changedInput schema / properties / topics / description
      Previous value: -"Topic tags the user wants updates on (e.g., ['deals', 'schedule_changes', 'new_services'])"New value: +"Topic tags (e.g., ['deals', 'schedule_changes'])"
    • changedInput schema / required
      Previous value: -[
-  "slug",
-  "contact_email",
-  "topics"
-]New value: +[
+  "slug",
+  "contact_email",
+  "topics",
+  "idempotency_key"
+]
  5. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / agent_id / description
      Previous value: -"Optional agent identifier"New value: +"Optional caller-asserted agent identifier; recorded for attribution"
    • changedInput schema / properties / contact_email / description
      Previous value: -"Email to subscribe — confirmed via returned token"New value: +"Email to subscribe — must be confirmed via the returned token before any updates send"
    • addedInput schema / properties / contact_email / format
      Added value: +"email"
    • removedInput schema / properties / contact_email / minLength
      Removed value: -1
    • removedInput schema / properties / idempotency_key
      Removed value: -{
-  "description": "Idempotency key",
-  "minLength": 1,
-  "type": "string"
-}
    • changedInput schema / properties / slug / description
      Previous value: -"Business slug identifier"New value: +"business slug"
    • changedInput schema / properties / topics / description
      Previous value: -"Topic tags (e.g., ['deals', 'schedule_changes'])"New value: +"Topic tags the user wants updates on (e.g., ['deals', 'schedule_changes', 'new_services'])"
    • changedInput schema / required
      Previous value: -[
-  "slug",
-  "contact_email",
-  "topics",
-  "idempotency_key"
-]New value: +[
+  "slug",
+  "contact_email",
+  "topics"
+]
  6. Changed9 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / agent_id / description
      Previous value: -"Optional caller-asserted agent identifier; recorded for attribution"New value: +"Optional agent identifier"
    • changedInput schema / properties / contact_email / description
      Previous value: -"Email to subscribe — must be confirmed via the returned token before any updates send"New value: +"Email to subscribe — confirmed via returned token"
    • removedInput schema / properties / contact_email / format
      Removed value: -"email"
    • addedInput schema / properties / contact_email / minLength
      Added value: +1
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Idempotency key",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / slug / description
      Previous value: -"business slug"New value: +"Business slug identifier"
    • changedInput schema / properties / topics / description
      Previous value: -"Topic tags the user wants updates on (e.g., ['deals', 'schedule_changes', 'new_services'])"New value: +"Topic tags (e.g., ['deals', 'schedule_changes'])"
    • changedInput schema / required
      Previous value: -[
-  "slug",
-  "contact_email",
-  "topics"
-]New value: +[
+  "slug",
+  "contact_email",
+  "topics",
+  "idempotency_key"
+]
  7. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare mutation, idempotency, and destructive hints. The description adds useful behavioral context: the subscription is pending, only the user can confirm it, the confirmation URL expires in 7 days, and reusing an idempotency key returns the original subscription.

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 tight sentences with no wasted words. The pending-subscription constraint and idempotency behavior are front-loaded and easy to scan.

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 and annotations, the description is complete enough for an agent to invoke it correctly. It covers the pending state, confirmation requirement, expiry window, and idempotency behavior.

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 schema already documents parameters. The description adds meaning beyond the schema by explaining the idempotency_key reuse behavior and the email confirmation flow.

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: 'Start a pending email subscription to updates from a business.' This clearly distinguishes the tool from booking, payment, quote, and callback siblings.

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

Usage Guidelines3/5

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

Usage is implied by the description, but it does not explicitly state when to use this tool versus alternatives or when not to use it. The confirmation workflow is explained, but selection guidance is absent.

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

All Advocate toolsInspect
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.

Resources