ActivitySmith

End Live Activity Stream

end_live_activity_stream

Destructive

End the current Live Activity for a managed stream and remove the stream key. Use it when the tracked work is finished; to stop updates temporarily and keep the key, use pause_live_activity_stream instead. A later set_live_activity_stream call with the same key starts a new Live Activity. Ending remotely also uses the device's ActivityKit push budget, so end once for a genuine lifecycle completion and do not repeatedly end and recreate a stream to refresh it.

Input Schema

Name	Required	Description
`tags`	No	Optional final Tags. Omit to preserve; send [] to clear.
`alert`	No	Optional APNs alert payload for the ending update.
`action`	No	Optional action button/tap target. Use { title, type: "open_url", url } with an HTTP/HTTPS URL or shortcuts://run-shortcut?name=... to open a URL or run an iPhone Shortcut. Use { title, type: "webhook", url, method, body } to call an HTTPS webhook. Webhook method can be GET or POST.
`metadata`	No	Optional final app-only details. Omit to preserve; send {} to clear.
`stream_key`	Yes	Stable Live Activity stream key. Use the same key to update the same stream. Do not create new keys for routine updates: every new stream requires another remote start and uses the device's limited iOS push-to-start budget. Use only letters, numbers, underscores, and hyphens.
`content_state`	No	Optional final Live Activity content state. If omitted, ActivitySmith uses the latest stored state when possible.
`secondary_action`	No	Optional secondary action button for alert, progress, and segmented_progress Live Activities. Uses the same object shape as action.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026

addedInput schema / properties / action / anyOf

Added value: +[
+  {
+    "properties": {
+      "body": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Webhook only: optional JSON object sent with the request."
+      },
+      "method": {
+        "description": "Webhook only: GET or POST. Defaults to POST.",
+        "pattern": "^(GET|POST)$",
+        "type": "string"
+      },
+      "title": {
+        "description": "Button label shown on the Live Activity.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "type": {
+        "description": "open_url opens url on the iPhone. webhook makes ActivitySmith call url when the button is tapped.",
+        "enum": [
+          "open_url",
+          "webhook"
+        ],
+        "type": "string"
+      },
+      "url": {
+        "description": "For open_url: an http or https URL, or shortcuts://run-shortcut?name=... to run an iPhone Shortcut. Other app URL schemes are rejected. For webhook: an https URL.",
+        "maxLength": 2048,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "title",
+      "type",
+      "url"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / secondary_action / anyOf

Added value: +[
+  {
+    "properties": {
+      "body": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Webhook only: optional JSON object sent with the request."
+      },
+      "method": {
+        "description": "Webhook only: GET or POST. Defaults to POST.",
+        "pattern": "^(GET|POST)$",
+        "type": "string"
+      },
+      "title": {
+        "description": "Button label shown on the Live Activity.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "type": {
+        "description": "open_url opens url on the iPhone. webhook makes ActivitySmith call url when the button is tapped.",
+        "enum": [
+          "open_url",
+          "webhook"
+        ],
+        "type": "string"
+      },
+      "url": {
+        "description": "For open_url: an http or https URL, or shortcuts://run-shortcut?name=... to run an iPhone Shortcut. Other app URL schemes are rejected. For webhook: an https URL.",
+        "maxLength": 2048,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "title",
+      "type",
+      "url"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 18, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark this as destructive and open-world, but the description adds important context beyond them: it removes the stream key, ending remotely consumes the device's ActivityKit push budget, and repeatedly ending and recreating a stream to refresh it should be avoided. These are exactly the operational caveats an agent needs before invoking a destructive lifecycle operation.

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 front-loaded with the action and scope, then immediately routes to the alternative and adds the lifecycle/budget caveat. Every sentence contributes useful selection or safety information, with no filler.

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 destructive annotations, rich 7-parameter schema, and presence of an output schema, the description supplies the remaining decision-critical context: what gets removed, when to prefer the sibling pause operation, and the push-budget consequence of repeated end/recreate cycles.

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 detailed parameter semantics are already supplied by the input schema. The description reinforces the stability and lifecycle meaning of stream_key, but it does not add materially beyond the schema for the other six parameters, so the baseline 3 is appropriate.

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: ending the current Live Activity for a managed stream and removing its stream key. It clearly distinguishes the operation from sibling alternatives such as pause_live_activity_stream and set_live_activity_stream, so an agent can select it without opening the schema.

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 gives explicit when-to-use guidance: use when tracked work is finished, whereas pausing is for temporarily stopping updates while keeping the key. It also clarifies lifecycle behavior by noting that a later set_live_activity_stream call with the same key starts a new Live Activity.

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

All ActivitySmith tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?