StudioSphere Pulse — Audio Intelligence

purchase_token_pack

Create a Stripe Checkout session for a Pulse token pack. Returns payment_url — DO NOT submit it programmatically; surface it to the user so they can complete payment in their browser. Once paid, banked tokens are credited automatically. Requires PULSE_API_KEY.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pack`	Yes	Token pack tier

Output Schema

TableJSON Schema

Name	Required	Description
`pack`	No	Token-pack tier label.
`error`	No	Machine-readable error code.
`tokens`	No	Tokens included in the pack.
`details`	No	Additional structured context from Pulse.
`message`	No	Human-readable recovery guidance.
`currency`	No	Checkout currency.
`retryable`	No	Whether the caller may retry after changing state or waiting.
`amount_usd`	No	Pack price in USD.
`expires_at`	No	ISO timestamp when the Checkout link expires.
`payment_url`	No	Stripe Checkout URL to present to the user.
`purchase_id`	No	Pulse token-pack purchase id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / pack / enum

Previous value: -[
-  "10K",
-  "50K",
-  "200K"
-]New value: +[
+  "1K",
+  "10K",
+  "50K",
+  "200K"
+]

Changed3 schema fields changedJun 19, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "purchase_id",
+      "pack",
+      "tokens",
+      "amount_usd",
+      "currency",
+      "payment_url",
+      "expires_at"
+    ]
+  },
+  {
+    "required": [
+      "error",
+      "message"
+    ]
+  }
+]

addedOutput schema / properties

Added value: +{
+  "amount_usd": {
+    "description": "Pack price in USD.",
+    "type": "number"
+  },
+  "currency": {
+    "description": "Checkout currency.",
+    "type": "string"
+  },
+  "details": {
+    "additionalProperties": true,
+    "description": "Additional structured context from Pulse.",
+    "type": "object"
+  },
+  "error": {
+    "description": "Machine-readable error code.",
+    "type": "string"
+  },
+  "expires_at": {
+    "description": "ISO timestamp when the Checkout link expires.",
+    "type": "string"
+  },
+  "message": {
+    "description": "Human-readable recovery guidance.",
+    "type": "string"
+  },
+  "pack": {
+    "description": "Token-pack tier label.",
+    "type": "string"
+  },
+  "payment_url": {
+    "description": "Stripe Checkout URL to present to the user.",
+    "type": "string"
+  },
+  "purchase_id": {
+    "description": "Pulse token-pack purchase id.",
+    "type": "string"
+  },
+  "retryable": {
+    "description": "Whether the caller may retry after changing state or waiting.",
+    "type": "boolean"
+  },
+  "tokens": {
+    "description": "Tokens included in the pack.",
+    "type": "number"
+  }
+}

addedOutput schema / required
```
Added value: +[]
```

Changed1 schema field changedMay 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

AddedMay 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only cover safety hints (openWorldHint, non-idempotent, non-destructive); the description adds substantive context they cannot convey: the required PULSE_API_KEY, the asynchronous post-condition that tokens are credited after payment, and a hard prohibition on programmatic URL submission. It does not cover retry/idempotency semantics for repeated session creation, which matters for a non-idempotent tool.

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?

Three tight sentences, purpose front-loaded, then the critical output-handling warning, then the auth prerequisite. No filler, and the most failure-prone instruction gets due prominence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the return value need not be explained, and the auth requirement plus post-payment crediting are stated, so an agent has enough to invoke it correctly. The one gap is routing versus request_payment_link, which the description never addresses.

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?

Only one parameter and schema description coverage is 100%, so the schema fully documents 'pack' including its enum tiers. The description adds no meaning about tier choice or relative value, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Create a Stripe Checkout session for a Pulse token pack.' This clearly separates it from readers like get_token_balance and list_token_packs, but it does not distinguish itself from the sibling request_payment_link, which sounds like an overlapping purchasing path.

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?

Gives a clear operational constraint — do not submit the returned URL programmatically, surface it to the user instead — which tells the agent exactly how the tool is meant to be consumed. It does not state when to choose it over list_token_packs or request_payment_link, so an explicit alternative-selection rule is missing.

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

All StudioSphere Pulse — Audio Intelligence 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.