Skip to main content
Glama

StudioSphere Pulse — Audio Intelligence

by space.studiosphere

request_payment_link

Generate a one-time Stripe payment page for users without a Pulse account. Before calling, you MUST confirm with the user that they have a lawful basis to submit this audio for analysis; for a user-requested batch/folder/project, one confirmation can cover that scope. Present the payment_url to the user as a link. Analysis begins automatically after payment. Poll get_job_status with the returned job_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_estimate_idYesThe job_estimate_id returned by estimate_cost.
attestation_confirmedYesSet 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoMachine-readable error code.
job_idNoPulse job id for polling after payment.
dedupedNoTrue when an existing active Checkout link was reused.
detailsNoAdditional structured context from Pulse.
messageNoHuman-readable recovery guidance.
retryableNoWhether the caller may retry after changing state or waiting.
expires_atNoISO timestamp when the Checkout link expires.
payment_urlNoStripe Checkout URL to present to the user.
cost_displayNoHuman-readable estimated cost.
charged_displayNoHuman-readable upfront Checkout charge.
amount_charged_centsNoStripe Checkout charge in cents.
amount_estimate_centsNoEstimated usage value in cents.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • 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: +[]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. Changed1 schema field changed
    • 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."
  4. Changed2 schema fields changed
    • 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"
+]
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses key behavioral traits beyond annotations: analysis begins automatically after payment (side effect), the page is one-time (non-idempotent), confirmation is required, and the returned job_id is for polling. This provides rich operational context that annotations alone lack.

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 four sentences, each delivering essential information: purpose, precondition, output handling, and follow-up. No filler or redundancy; it is well-structured and front-loaded with the primary purpose.

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?

The description covers the critical workflow steps (confirmation, presenting the URL, polling) and leverages the existing output schema for return values. It lacks explicit failure/error handling or payment status edge cases, but for a tool with this schema richness, it is sufficiently complete.

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?

While schema descriptions cover both parameters fully (100% coverage), the description adds nuance to attestation_confirmed by explaining that one confirmation can cover a batch/folder/project scope. This enriches understanding of the boolean parameter beyond the schema's basic 'only after user confirms'.

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 clearly states the tool generates a one-time Stripe payment page for users without a Pulse account, distinguishing it from sibling payment tools like purchase_token_pack. It also outlines the full flow (confirmation, payment, polling), leaving no ambiguity about its function.

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?

It specifies when to use the tool ('for users without a Pulse account') and includes mandatory preconditions (confirmation) and follow-up steps (present link, poll get_job_status). However, it does not explicitly name alternatives or when not to use it, though the context implies exclusions.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct role: cost estimation, analysis initiation, status polling, token balance, token pack listing/purchasing, payment linking, and trial creation. Even the two analysis-triggering tools (analyze_track and request_payment_link) are cleanly separated by account vs. non-account workflows.

Naming Consistency5/5

All eight tools follow a consistent snake_case verb_noun pattern (e.g., estimate_cost, list_token_packs, start_trial). The verbs are specific and predictable, and there are no mixed conventions or vague names.

Tool Count5/5

Eight tools strike a good balance for this domain: three cover the analysis pipeline (estimate, analyze, poll) and five cover billing/tokens/trial. Every tool serves a distinct purpose with no redundancy or bloat.

Completeness4/5

The set covers the full analysis workflow (cost estimation, submission, status polling) and token management (balance, packs, purchase, trial, payment link). A minor gap is the lack of job cancellation or historical job listing, but core user tasks are fully supported.

Resources