Skip to main content
Glama

StudioSphere Pulse — Audio Intelligence

by space.studiosphere

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.
banked_tokensNoCurrent banked-token balance.
api_key_prefixNoRedacted API-key prefix.
trial_expires_atNoTrial expiry timestamp if this is a trial account.
account_created_atNoAccount creation timestamp.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds authentication context ('Requires PULSE_API_KEY', 'authenticated Pulse account'), which is useful beyond annotations. It does not explain 'banked' but the output schema covers return values.

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 two short sentences, front-loaded with the primary action. 'Requires PULSE_API_KEY' is a necessary warning with no filler. Every word 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?

The tool is a simple read-only balance check with no parameters. Annotations cover safety, output schema covers return format, and the description covers authentication. This is complete for an agent to select and invoke the tool 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 input schema has zero parameters, so the description cannot add parameter syntax. It does clarify that the balance is for the authenticated account, which provides implicit context. Baseline 4 is appropriate for a no-parameter tool.

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 uses the specific verb 'Check' with a clear resource, 'banked token balance', scoped to 'the authenticated Pulse account'. This clearly distinguishes it from sibling tools like list_token_packs (available packs) and purchase_token_pack (buying).

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 states a precondition: 'Requires PULSE_API_KEY.' It does not name alternatives, but the tool's purpose is unambiguous, making the usage context clear. No exclusions are needed given the simple read-only nature.

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