StudioSphere Pulse — Audio Intelligence

get_job_status

Read-onlyIdempotent

Resume the original saved job anonymously after interruption. Follow continuation for human payment, bounded polling, result review or support; never create a replacement purchase. Completed/partial results may include studio_notes: preserve provenance, warnings and failed tools; BPM/key are estimates requiring review. Keep job references private. Results, costs and notes are not payment/refund confirmation. refund_status_source=local_ledger is reconciliation at refund_checked_at, not a fresh provider query; unconfirmed/needs_review is not a completed refund. Review terminal Checkout billing separately on the result page or the on-demand REST receipt_api_url; that URL is not another MCP tool.

Input Schema

Name	Required	Description
`job_id`	Yes	The job_id returned by analyze_track or request_payment_link.
`include_waveform_data`	No	Optional. Defaults to false so chat agents receive a compact waveform summary plus result_url. Set true only if raw waveform samples are needed.
`include_waveform_image`	No	Optional. Defaults to true. When the job has waveform data, include a server-rendered PNG as MCP image content so the client can display it without fetching a URL.

Output Schema

Name	Required	Description
`error`	No	Machine-readable error code.
`job_id`	No	Pulse analysis job id.
`status`	No	Current or terminal job status.
`billing`	No
`details`	No	Additional structured context from Pulse.
`message`	No	Human-readable recovery guidance.
`results`	No	Analysis results when available.
`cost_usd`	No
`metadata`	No	Analysis metadata, including asset type, source hints, library metadata, and confidence policy when available.
`retryable`	No	Whether the caller may retry after changing state or waiting.
`expires_at`	No
`result_url`	No	Public result page URL.
`completed_at`	No
`continuation`	No	Advisory saved-job recovery. URLs contain a private job reference. No provider read or settlement verification is performed.
`studio_notes`	No	Optional plain-text project notes for completed/partial usable results. Preserve review warnings, provenance and failed tools. Contains no audio/source URL or payment/refund receipt fields; job references are private.
`waveform_file`	No
`payment_source`	No
`tokens_charged`	No
`waveform_image`	No
`tokens_estimated`	No
`waveform_png_url`	No
`waveform_svg_url`	No
`result_provenance`	No	Per-tool provenance and applicability summary for interpreting detected, audio_candidate (manual review required), filename-sourced, suppressed, or low-confidence results.
`waveform_markdown`	No
`result_quality_notes`	No	Human-readable quality notes for suppressed, low-confidence, filename-sourced, or review-needed results.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / include_waveform_image / description

Previous value: -"Optional. Defaults to true. When the job has waveform data, include a server-rendered SVG as MCP image content so the client can display it without fetching a URL."New value: +"Optional. Defaults to true. When the job has waveform data, include a server-rendered PNG as MCP image content so the client can display it without fetching a URL."

Changed1 schema field changedOct 13, 2026

addedOutput schema / properties / studio_notes

Added value: +{
+  "description": "Optional plain-text project notes for completed/partial usable results. Preserve review warnings, provenance and failed tools. Contains no audio/source URL or payment/refund receipt fields; job references are private.",
+  "type": "string"
+}

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 7, 2026

changedOutput schema / properties / result_provenance / description

Previous value: -"Per-tool provenance and applicability summary for interpreting detected, filename-sourced, suppressed, or low-confidence results."New value: +"Per-tool provenance and applicability summary for interpreting detected, audio_candidate (manual review required), filename-sourced, suppressed, or low-confidence results."

Changed3 schema fields changedAug 5, 2026

addedOutput schema / properties / metadata

Added value: +{
+  "additionalProperties": true,
+  "description": "Analysis metadata, including asset type, source hints, library metadata, and confidence policy when available.",
+  "type": "object"
+}

addedOutput schema / properties / result_provenance

Added value: +{
+  "additionalProperties": true,
+  "description": "Per-tool provenance and applicability summary for interpreting detected, filename-sourced, suppressed, or low-confidence results.",
+  "type": "object"
+}

addedOutput schema / properties / result_quality_notes

Added value: +{
+  "description": "Human-readable quality notes for suppressed, low-confidence, filename-sourced, or review-needed results.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed3 schema fields changedJun 19, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "job_id",
+      "status"
+    ]
+  },
+  {
+    "required": [
+      "error",
+      "message"
+    ]
+  }
+]

addedOutput schema / properties

Added value: +{
+  "billing": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "completed_at": {
+    "type": "string"
+  },
+  "cost_usd": {
+    "type": "number"
+  },
+  "details": {
+    "additionalProperties": true,
+    "description": "Additional structured context from Pulse.",
+    "type": "object"
+  },
+  "error": {
+    "description": "Machine-readable error code.",
+    "type": "string"
+  },
+  "expires_at": {
+    "type": "string"
+  },
+  "job_id": {
+    "description": "Pulse analysis job id.",
+    "type": "string"
+  },
+  "message": {
+    "description": "Human-readable recovery guidance.",
+    "type": "string"
+  },
+  "payment_source": {
+    "type": "string"
+  },
+  "result_url": {
+    "description": "Public result page URL.",
+    "type": "string"
+  },
+  "results": {
+    "additionalProperties": true,
+    "description": "Analysis results when available.",
+    "type": "object"
+  },
+  "retryable": {
+    "description": "Whether the caller may retry after changing state or waiting.",
+    "type": "boolean"
+  },
+  "status": {
+    "description": "Current or terminal job status.",
+    "type": "string"
+  },
+  "tokens_charged": {
+    "type": "number"
+  },
+  "tokens_estimated": {
+    "type": "number"
+  },
+  "waveform_file": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "waveform_image": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "waveform_markdown": {
+    "type": "string"
+  },
+  "waveform_png_url": {
+    "type": "string"
+  },
+  "waveform_svg_url": {
+    "type": "string"
+  }
+}

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

addedInput schema / properties / include_waveform_image

Added value: +{
+  "description": "Optional. Defaults to true. When the job has waveform data, include a server-rendered SVG as MCP image content so the client can display it without fetching a URL.",
+  "type": "boolean"
+}

Changed1 schema field changedMay 2, 2026

addedInput schema / properties / include_waveform_data

Added value: +{
+  "description": "Optional. Defaults to false so chat agents receive a compact waveform summary plus result_url. Set true only if raw waveform samples are needed.",
+  "type": "boolean"
+}

First observedMay 1, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint, so the safety profile is covered; the description adds meaningful context beyond that: refund_status_source=local_ledger is reconciliation at refund_checked_at and not a fresh provider query, unconfirmed/needs_review is not a completed refund, and results are not payment confirmation. It also warns to preserve provenance and keep job references private. The 'Resume' framing slightly muddies the read-only picture but does not state a mutation.

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

Conciseness2/5

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

The text is a dense run-on of billing, refund-reconciliation and checkpoint caveats, none of which is front-loaded as the primary purpose. Core information (what the tool returns) is buried behind refund_checked_at/local_ledger detail, and several sentences could be shortened or moved to the result documentation.

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

Completeness3/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, and the description does cover the shape of results (studio_notes, BPM/key estimates, warnings, failed tools). What is missing is a clear statement of the tool's core retrieval behavior and job lifecycle, leaving the agent to reconstruct the primary contract from side remarks.

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%, with job_id, include_waveform_data and include_waveform_image all documented in the schema, so the baseline is 3. The description adds nothing about any parameter, not even the job_id that analyze_track or request_payment_link produces.

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

Purpose3/5

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

The opening sentence frames the tool as resuming a saved job rather than plainly stating that it retrieves the status/result of an analysis job by job_id. The follow-on clauses about results, refunds and billing hint at what is returned, but an agent must infer the core verb+resource. It is distinguishable from siblings only indirectly.

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?

It does give usage contexts (follow continuation for payment, bounded polling, result review, support) and a prohibition (never create a replacement purchase), which implicitly routes away from purchase_token_pack/request_payment_link. However, the alternatives are never named and no sibling tool is explicitly contrasted, so the guidance is implied rather than explicit.

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.

get_job_status

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources