Skip to main content
Glama

StudioSphere Pulse — Audio Intelligence

by space.studiosphere
OverviewDiscussionsAdmin

get_token_balance

Read-onlyIdempotent

Check the banked token balance for the authenticated Pulse account. Requires PULSE_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoMachine-readable error code.
detailsNoAdditional structured context from Pulse.
messageNoHuman-readable recovery guidance.
retryableNoWhether the caller may retry after changing state or waiting.
account_typeNoPulse account type.
trial_policyNo
banked_tokensNoCurrent banked-token balance.
api_key_prefixNoRedacted API-key prefix.
trial_allowanceNo
trial_expires_atNoTrial expiry timestamp if this is a trial account.
account_created_atNoAccount creation timestamp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+}
  2. Changed3 schema fields changed
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "banked_tokens",
+      "api_key_prefix",
+      "account_type",
+      "trial_expires_at",
+      "account_created_at"
+    ]
+  },
+  {
+    "required": [
+      "error",
+      "message"
+    ]
+  }
+]
    • addedOutput schema / properties
      Added value: +{
+  "account_created_at": {
+    "description": "Account creation timestamp.",
+    "type": "string"
+  },
+  "account_type": {
+    "description": "Pulse account type.",
+    "type": "string"
+  },
+  "api_key_prefix": {
+    "description": "Redacted API-key prefix.",
+    "type": "string"
+  },
+  "banked_tokens": {
+    "description": "Current banked-token balance.",
+    "type": "number"
+  },
+  "details": {
+    "additionalProperties": true,
+    "description": "Additional structured context from Pulse.",
+    "type": "object"
+  },
+  "error": {
+    "description": "Machine-readable error code.",
+    "type": "string"
+  },
+  "message": {
+    "description": "Human-readable recovery guidance.",
+    "type": "string"
+  },
+  "retryable": {
+    "description": "Whether the caller may retry after changing state or waiting.",
+    "type": "boolean"
+  },
+  "trial_expires_at": {
+    "description": "Trial expiry timestamp if this is a trial account.",
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}
    • addedOutput schema / required
      Added value: +[]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds a genuinely useful behavioral detail beyond the annotations: the PULSE_API_KEY authentication requirement, which the rubric explicitly counts as credit-worthy context.

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?

Two short sentences with zero filler; the purpose is front-loaded and the auth constraint follows immediately. Nothing is wasted.

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 the description need not explain return values, and with no input parameters there is little else to document. Purpose plus auth requirement is sufficient for an agent to call this correctly.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to clarify beyond the auth context it already provides.

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?

States a specific verb ('Check') and resource ('banked token balance') scoped to the authenticated Pulse account. This is clearly distinguishable from sibling tools like list_token_packs or purchase_token_pack, which deal with packs rather than balance.

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?

Usage is implied (query the current balance), but there is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The auth prerequisite is stated but that is a precondition, not routing guidance.

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
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.

Resources