StudioSphere Pulse — Audio Intelligence

get_job_status

Read-onlyIdempotent

Check the status and results of an analysis job. Poll after analyze_track returns job_id, or after the user pays via request_payment_link. Returns full results when status=completed.

Input Schema

TableJSON 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 SVG as MCP image content so the client can display it without fetching a URL.

Output Schema

TableJSON 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
`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, 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.

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

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds behavioral context by specifying the polling pattern and that full results come only when status=completed. This goes beyond the annotations and does not contradict them.

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 concise, with three short sentences, each serving a distinct purpose: state the main action, give the polling trigger, and describe the completion condition. It is front-loaded and every sentence earns its place.

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 presence of a detailed input schema and an output schema, the description covers the essential usage context: what the tool does, when to call it, and what result to expect. It does not need to explain return values or parameter specifics since the schema handles those.

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?

The input schema has complete descriptions for all three parameters, including defaults and effects, so the description does not need to add param semantics. The description's mention of job_id origin and result conditions adds no new parameter-level information beyond the schema.

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's function with a specific verb ('Check') and resource ('status and results of an analysis job'). It also ties the tool's use to the job lifecycle (after analyze_track or payment), distinguishing it from sibling tools like analyze_track and request_payment_link.

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?

The description explicitly tells the agent when to use the tool: poll after analyze_track returns job_id or after the user pays via request_payment_link. It does not list when-not-to-use cases or alternatives, but the provided timing guidance is clear and actionable.

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