ACE Music MCP Server by useapi.net (third-party)

Get an account with live credits

acemusic_get_account

Read-onlyIdempotent

Read one account live from ACE Music: plan, credits left, the models it can use with their text limits, and credit costs (a song request 4, stems 5 / 60). Use it before a paid request to check the balance; acemusic_list_accounts is the stored, offline view. GET /accounts/{email}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>"
    },
    "name": "acemusic_get_account"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes	The account email.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral context beyond those annotations: it is the live account view, it returns plan and credit information, and it should be used before paid requests. It does not cover authentication, rate limits, or error behavior, so it is strong but not exhaustive.

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 compact and front-loaded: it states what is read, what is returned, when to use it, and the sibling alternative. Every sentence earns its place without redundant restatement of the title.

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?

With no output schema, the description usefully enumerates the returned live account fields: plan, credits left, models, text limits, and credit costs. It also supplies usage guidance and the offline sibling alternative, which is enough for an agent to call this one-parameter read tool correctly.

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?

Schema description coverage is 100% and the single email parameter is already documented in the schema. The description reinforces the email path via GET /accounts/{email}, but adds no syntax or format detail beyond the structured 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 states a specific verb and resource: read one account live from ACE Music, with enumerated return content such as plan, credits left, models, text limits, and credit costs. It explicitly distinguishes this tool from the sibling acemusic_list_accounts by calling that the stored, offline view.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: check the balance before a paid request. It also names the alternative tool acemusic_list_accounts and explains the selecting condition: live account data versus the stored, offline view.

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

All ACE Music MCP Server by useapi.net (third-party) 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.

Resources

Need Help?