Skip to main content
Glama

check_credit_balance

View available credits for generating AI-powered music through natural language commands, enabling song creation with direct download links.

Instructions

Check your credit balance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
typeYes
_metaNo
annotationsNo

Implementation Reference

  • The handler function for the 'check_credit_balance' MCP tool. It is decorated with @mcp.tool, making this both the implementation and registration point. The function checks the user's credit balance by querying the MusicMCP.AI API's /credit endpoint and returns a TextContent with the balance or error message.
    @mcp.tool(description="Check your credit balance.")
    async def check_credit_balance() -> TextContent:
        """Check credit balance"""
        try:
            if not api_key:
                raise Exception("Cannot find API key. Please set MUSICMCP_API_KEY environment variable.")
    
            url = f"{api_url}/credit"
            headers = {'api-key': api_key}
    
            async with httpx.AsyncClient(timeout=httpx.Timeout(30.0)) as client:
                response = await client.get(url, headers=headers)
                response.raise_for_status()
                result = response.json()
    
            # API response format: {success, message, data}
            if not result or not result.get("success"):
                error_msg = result.get("message", "Unknown error")
                return TextContent(type="text", text=f"❌ Credit balance check failed: {error_msg}")
    
            data = result.get("data", {})
            if data.get("valid"):
                has_credits = data.get("hasCredits", False)
                credits = data.get("credits", 0)
                if has_credits:
                    return TextContent(
                        type="text",
                        text=f"✅ API key is valid! You have {credits} credits remaining."
                    )
                else:
                    return TextContent(
                        type="text",
                        text="⚠️ API key is valid but you have insufficient credits. Please recharge."
                    )
            else:
                return TextContent(type="text", text="❌ API key is invalid.")
    
        except Exception as e:
            return TextContent(type="text", text=f"❌ Failed to check credit balance: {str(e)}")
  • The @mcp.tool decorator registers the 'check_credit_balance' tool with the MCP server, providing a description for the tool schema.
    @mcp.tool(description="Check your credit balance.")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Check' implies a read-only operation, but the description doesn't specify authentication requirements, rate limits, response format, or whether this affects system state. For a financial tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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?

The description is extremely concise - a single four-word sentence that communicates the core purpose without unnecessary elaboration. While perhaps too minimal for optimal clarity, it's efficiently structured with zero wasted words.

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?

Given the tool has zero parameters, 100% schema coverage, and an output schema exists, the description's minimalism is somewhat acceptable. However, for a financial balance check with no annotations, the description should ideally specify what type of credits, for which account/system, and basic behavioral context to be truly complete.

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 has zero parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for matching the schema's completeness regarding inputs.

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 description 'Check your credit balance' clearly states the action (check) and resource (credit balance), making the basic purpose understandable. However, it doesn't differentiate this tool from its siblings (health check, song generation tools) or specify what system/account's credit balance is being checked, leaving room for ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, frequency recommendations, or comparison to sibling tools like check_api_health. The agent must infer usage context entirely from the tool name and description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/amCharlie/aimusic-mcp-tool'

If you have feedback or need assistance with the MCP directory API, please join our Discord server