StudioSphere Pulse — Audio Intelligence

request_payment_link

Create anonymous one-off Checkout after an estimate, explicit human link-creation approval and lawful-basis confirmation. Read analysis_options.checkout. The human reviews the hosted upfront amount and pays; it can exceed analysis cost. Save job_id, payment_url and continuation.review_url privately; lost links require support, not a replacement purchase. For minimum_charge_offer, show minimum final cost and upfront estimate, obtain explicit acceptance, then send accept_minimum_charge:true and max_upfront_amount_cents at the approved ceiling. Rights alone do not approve spending. On estimate_pricing_changed, get a fresh free estimate and explicit approval. An exceeded cap needs new review; never raise it or retry automatically. Poll the original job with get_job_status after payment or interruption. Host setup/recovery: https://pulse.studiosphere.space/connect

Input Schema

Name	Required	Description
`job_estimate_id`	Yes	The job_estimate_id returned by estimate_cost.
`accept_minimum_charge`	No	Optional. Set true only after explicit human acceptance of minimum_charge_offer.minimum_final_cost_usd and its estimated upfront payment. Rights confirmation alone is not spending approval.
`attestation_confirmed`	Yes	Set to true ONLY after the user has confirmed they have rights, permission, lawful access, or another legal basis to submit this audio, or the current user-requested batch/folder/project containing it, for analysis.
`max_upfront_amount_cents`	No	Optional approved upfront USD ceiling in whole cents; required for minimum-charge acceptance. The gateway rejects a higher charge before creating a purchase. Do not raise it without renewed human approval.

Output Schema

Name	Required	Description
`error`	No	Machine-readable error code.
`job_id`	No	Pulse job id for polling after payment.
`deduped`	No	True when an existing active Checkout link was reused.
`details`	No	Additional structured context from Pulse.
`message`	No	Human-readable recovery guidance.
`retryable`	No	Whether the caller may retry after changing state or waiting.
`expires_at`	No	ISO timestamp when the Checkout link expires.
`payment_url`	No	Stripe Checkout URL to present to the user.
`continuation`	No	Advisory saved-job recovery. URLs contain a private job reference. No provider read or settlement verification is performed.
`cost_display`	No	Human-readable estimated cost.
`charged_display`	No	Human-readable upfront Checkout charge.
`amount_charged_cents`	No	Stripe Checkout charge in cents.
`amount_estimate_cents`	No	Estimated usage value in cents.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 12, 2026

addedInput schema / properties / accept_minimum_charge

Added value: +{
+  "description": "Optional. Set true only after explicit human acceptance of minimum_charge_offer.minimum_final_cost_usd and its estimated upfront payment. Rights confirmation alone is not spending approval.",
+  "type": "boolean"
+}

addedInput schema / properties / max_upfront_amount_cents

Added value: +{
+  "description": "Optional approved upfront USD ceiling in whole cents; required for minimum-charge acceptance. The gateway rejects a higher charge before creating a purchase. Do not raise it without renewed human approval.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

Changed1 schema field changedOct 12, 2026

addedOutput schema / properties / continuation

Added value: +{
+  "additionalProperties": false,
+  "description": "Advisory saved-job recovery. URLs contain a private job reference. No provider read or settlement verification is performed.",
+  "properties": {
+    "action": {
+      "enum": [
+        "complete_checkout",
+        "wait",
+        "review_results",
+        "contact_support",
+        "check_saved_job"
+      ],
+      "type": "string"
+    },
+    "arguments": {
+      "additionalProperties": false,
+      "properties": {
+        "job_id": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "job_id"
+      ],
+      "type": "object"
+    },
+    "automatic_resubmission_allowed": {
+      "const": false,
+      "type": "boolean"
+    },
+    "financial_status_verified": {
+      "const": false,
+      "type": "boolean"
+    },
+    "guidance": {
+      "type": "string"
+    },
+    "max_poll_attempts": {
+      "minimum": 1,
+      "type": "integer"
+    },
+    "missing_payment_url_action": {
+      "const": "contact_support",
+      "type": "string"
+    },
+    "poll_after_seconds": {
+      "minimum": 1,
+      "type": "integer"
+    },
+    "receipt_api_url": {
+      "type": "string"
+    },
+    "review_url": {
+      "type": "string"
+    },
+    "status_url": {
+      "type": "string"
+    },
+    "support_email": {
+      "type": "string"
+    },
+    "tool": {
+      "const": "get_job_status",
+      "type": "string"
+    }
+  },
+  "required": [
+    "action",
+    "tool",
+    "arguments",
+    "status_url",
+    "review_url",
+    "automatic_resubmission_allowed",
+    "financial_status_verified",
+    "support_email",
+    "guidance"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 12, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "payment_url",
-      "job_id",
-      "cost_display",
-      "charged_display",
-      "amount_charged_cents",
-      "amount_estimate_cents",
-      "expires_at"
-    ]
-  },
-  {
-    "required": [
-      "error",
-      "message"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "payment_url",
+      "job_id",
+      "cost_display",
+      "charged_display",
+      "amount_charged_cents",
+      "amount_estimate_cents",
+      "expires_at"
+    ]
+  },
+  {
+    "required": [
+      "error",
+      "message"
+    ]
+  },
+  {
+    "properties": {
+      "deduped": {
+        "const": true
+      }
+    },
+    "required": [
+      "payment_url",
+      "job_id",
+      "cost_display",
+      "expires_at",
+      "deduped"
+    ]
+  }
+]

Changed3 schema fields changedJun 19, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "payment_url",
+      "job_id",
+      "cost_display",
+      "charged_display",
+      "amount_charged_cents",
+      "amount_estimate_cents",
+      "expires_at"
+    ]
+  },
+  {
+    "required": [
+      "error",
+      "message"
+    ]
+  }
+]

addedOutput schema / properties

Added value: +{
+  "amount_charged_cents": {
+    "description": "Stripe Checkout charge in cents.",
+    "type": "number"
+  },
+  "amount_estimate_cents": {
+    "description": "Estimated usage value in cents.",
+    "type": "number"
+  },
+  "charged_display": {
+    "description": "Human-readable upfront Checkout charge.",
+    "type": "string"
+  },
+  "cost_display": {
+    "description": "Human-readable estimated cost.",
+    "type": "string"
+  },
+  "deduped": {
+    "description": "True when an existing active Checkout link was reused.",
+    "type": "boolean"
+  },
+  "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"
+  },
+  "job_id": {
+    "description": "Pulse job id for polling after payment.",
+    "type": "string"
+  },
+  "message": {
+    "description": "Human-readable recovery guidance.",
+    "type": "string"
+  },
+  "payment_url": {
+    "description": "Stripe Checkout URL to present to the user.",
+    "type": "string"
+  },
+  "retryable": {
+    "description": "Whether the caller may retry after changing state or waiting.",
+    "type": "boolean"
+  }
+}

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

Changed1 schema field changedMay 2, 2026

changedOutput schema / (root)

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

Changed1 schema field changedMay 2, 2026

changedInput schema / properties / attestation_confirmed / description

Previous value: -"Set to true ONLY after the user has confirmed they have rights, permission, lawful access, or another legal basis to submit this audio for analysis."New value: +"Set to true ONLY after the user has confirmed they have rights, permission, lawful access, or another legal basis to submit this audio, or the current user-requested batch/folder/project containing it, for analysis."

Changed2 schema fields changedMay 1, 2026

addedInput schema / properties / attestation_confirmed

Added value: +{
+  "description": "Set to true ONLY after the user has confirmed they have rights, permission, lawful access, or another legal basis to submit this audio for analysis.",
+  "type": "boolean"
+}

changedInput schema / required

Previous value: -[
-  "job_estimate_id"
-]New value: +[
+  "job_estimate_id",
+  "attestation_confirmed"
+]

First observedMay 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, it discloses that the hosted upfront amount is reviewed and paid by a human, may exceed the analysis cost, and that lost links require support rather than replacement purchase. It also explains cap enforcement, no automatic retries, and the consequence of exceeded limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and then branches into required workflow details. It is dense but largely earn-place content; however, its length and high instruction density make it closer to operational policy than a concise tool summary.

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?

An output schema exists, so return values need not be explained. Given the complexity and risk of this payment-link tool, the description covers prerequisites, human approval, edge cases, recovery, and next steps comprehensively.

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 schema already documents all four parameters thoroughly. The description reinforces workflow conditions for accept_minimum_charge and max_upfront_amount_cents, but largely repeats the schema's guidance rather than adding new parameter semantics.

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 action and resource: creating an anonymous one-off Checkout/payment link. It situates the action after estimate_cost and human approval, clearly distinguishing it from estimation and token-pack purchase siblings.

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 prerequisites: an estimate must exist, a human must approve link creation, and lawful basis must be confirmed. It also handles branches for minimum_charge_offer, estimate_pricing_changed, exceeded caps, payment/interruption follow-up via get_job_status, and recovery support.

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.