StudioSphere Pulse — Audio Intelligence

start_trial

Start a temporary, email-free Pulse trial for one URL analysis. Read trial_policy and trial_allowance for the actual duration cap and remaining attempts; an existing trial key may have a lower cap. One completed/partial analysis consumes the allowance regardless of remaining tokens. A failed analysis may retry only when attempts remain. No Stripe Checkout session is created. Store the returned private API key in the client or a trusted local environment; never repost it in logs, screenshots, shared chats or issues. Confirm rights, permission, lawful access, or another legal basis before analysis. The original CC0 demo is https://pulse.studiosphere.space/assets/pulse-demo.mp3 (180 seconds); use it only if it fits the returned cap.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Machine-readable error code.
`api_key`	No	Temporary Pulse API key for the trial account. Treat as private; do not print it in public logs, screenshots, GitHub issues, shared chats, or directory examples.
`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 temporary key expires.
`usage_note`	No	Limits and usage guidance for the trial.
`account_type`	No	The account type created by this tool.
`analyze_path`	No	REST path for authenticated analysis.
`trial_policy`	No
`upgrade_path`	No	Path for converting to an account.
`banked_tokens`	No	Trial token balance granted.
`estimate_path`	No	REST path for free estimates.
`trial_allowance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "api_key",
-      "account_type",
-      "banked_tokens",
-      "expires_at",
-      "usage_note"
-    ]
-  },
-  {
-    "required": [
-      "error",
-      "message"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "api_key",
+      "account_type",
+      "banked_tokens",
+      "expires_at",
+      "usage_note",
+      "trial_policy",
+      "trial_allowance"
+    ]
+  },
+  {
+    "required": [
+      "error",
+      "message"
+    ]
+  }
+]

addedOutput schema / properties / trial_allowance

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "analyses_remaining": {
+      "type": "integer"
+    },
+    "attempts_remaining": {
+      "type": "integer"
+    },
+    "max_duration_sec": {
+      "type": "integer"
+    },
+    "state": {
+      "enum": [
+        "available",
+        "in_progress",
+        "used",
+        "exhausted"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "state",
+    "analyses_remaining",
+    "attempts_remaining",
+    "max_duration_sec"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / trial_policy

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "enabled": {
+      "type": "boolean"
+    },
+    "expires_in_hours": {
+      "type": "integer"
+    },
+    "max_duration_sec": {
+      "type": "integer"
+    },
+    "max_queued_attempts": {
+      "type": "integer"
+    },
+    "tokens": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "enabled",
+    "tokens",
+    "max_duration_sec",
+    "max_queued_attempts",
+    "expires_in_hours"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 3, 2026

changedOutput schema / properties / api_key / description

Previous value: -"Temporary Pulse API key for the trial account."New value: +"Temporary Pulse API key for the trial account. Treat as private; do not print it in public logs, screenshots, GitHub issues, shared chats, or directory examples."

Changed3 schema fields changedJun 19, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "api_key",
+      "account_type",
+      "banked_tokens",
+      "expires_at",
+      "usage_note"
+    ]
+  },
+  {
+    "required": [
+      "error",
+      "message"
+    ]
+  }
+]

addedOutput schema / properties

Added value: +{
+  "account_type": {
+    "description": "The account type created by this tool.",
+    "enum": [
+      "trial"
+    ],
+    "type": "string"
+  },
+  "analyze_path": {
+    "description": "REST path for authenticated analysis.",
+    "type": "string"
+  },
+  "api_key": {
+    "description": "Temporary Pulse API key for the trial account.",
+    "type": "string"
+  },
+  "banked_tokens": {
+    "description": "Trial token balance granted.",
+    "type": "number"
+  },
+  "details": {
+    "additionalProperties": true,
+    "description": "Additional structured context from Pulse.",
+    "type": "object"
+  },
+  "error": {
+    "description": "Machine-readable error code.",
+    "type": "string"
+  },
+  "estimate_path": {
+    "description": "REST path for free estimates.",
+    "type": "string"
+  },
+  "expires_at": {
+    "description": "ISO timestamp when the temporary key expires.",
+    "type": "string"
+  },
+  "message": {
+    "description": "Human-readable recovery guidance.",
+    "type": "string"
+  },
+  "retryable": {
+    "description": "Whether the caller may retry after changing state or waiting.",
+    "type": "boolean"
+  },
+  "upgrade_path": {
+    "description": "Path for converting to an account.",
+    "type": "string"
+  },
+  "usage_note": {
+    "description": "Limits and usage guidance for the trial.",
+    "type": "string"
+  }
+}

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

AddedMay 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already say readOnly=false, openWorld=true, idempotent=false, destructive=false, but the description adds crucial behavior: existing trial key may lower the cap, consumption semantics for completed/partial vs failed analyses, no Stripe Checkout, and secure handling of the returned private API key. No contradiction.

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?

Front-loaded with purpose and key constraints. Dense but every sentence carries operational, security, or legal meaning; could be made more scannable, but no significant waste.

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?

For a zero-parameter tool with an output schema and annotations covering safety, the description supplies all needed calling context: trial policy references, allowance/retry rules, payment distinction, key storage, and legal prerequisites. Return values are covered by the output schema.

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?

There are zero input parameters, so the baseline is 4. The description adds no parameter meaning because none exist, though it mentions a returned private API key and a demo URL.

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?

Specific verb (Start) and resource (temporary, email-free Pulse trial for one URL analysis). It also distinguishes itself from paid siblings by stating 'No Stripe Checkout session is created,' so an agent can tell it apart from purchase_token_pack or 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?

Gives clear conditions: read trial_policy and trial_allowance, one analysis consumes allowance, failed analysis retries only if attempts remain, no Stripe session, confirm legal basis. It does not name alternative tools or explicitly say when to prefer them, so not a 5.

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.