AI Manga & Anime Generator - Mangii MCP

Get API credits

manga.get_credits

Read-onlyIdempotent

Return the API wallet. Spendable is apiPackCredits plus packCredits after the account has ever purchased. Later ad/referral grants on that pack pool also spend. weeklyCredits is display-only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`include_notes`	No	When true (default), include a notes string explaining that weeklyCredits does not spend on API or MCP.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Machine error code such as invalid_request, insufficient_credits, or quality_forbidden.
`notes`	No	Wallet rules for agents.
`message`	No	Human-readable error. Never includes stack traces or internal paths.
`packCredits`	No	In-app pack credits. After a purchase (hasEverPurchasedCredits), the full current balance is included in spendableCredits, including later ad/referral grants. Never-purchased pack balances do not spend.
`weeklyCredits`	No	In-app weekly credits. Display-only for API/MCP.
`apiPackCredits`	No	Spendable API credits for generate tools.
`spendableCredits`	No	apiPackCredits plus packCredits when the account has ever purchased. Same number useApiCredit will spend.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 6, 2026

changedOutput schema / properties / packCredits / description

Previous value: -"In-app pack credits. Only the purchase-backed portion is included in spendableCredits."New value: +"In-app pack credits. After a purchase (hasEverPurchasedCredits), the full current balance is included in spendableCredits, including later ad/referral grants. Never-purchased pack balances do not spend."

changedOutput schema / properties / spendableCredits / description

Previous value: -"apiPackCredits plus purchase-backed packCredits. Same number useApiCredit will spend."New value: +"apiPackCredits plus packCredits when the account has ever purchased. Same number useApiCredit will spend."

Changed2 schema fields changedAug 23, 2026

changedOutput schema / properties / packCredits / description

Previous value: -"In-app pack credits. Not spent by API/MCP."New value: +"In-app pack credits. Only the purchase-backed portion is included in spendableCredits."

changedOutput schema / properties / spendableCredits / description

Previous value: -"Same as apiPackCredits."New value: +"apiPackCredits plus purchase-backed packCredits. Same number useApiCredit will spend."

AddedAug 23, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The annotations already declare readOnlyHint and idempotentHint, so the description adds valuable behavioral context: it explains the meaning of spendable credits, that weeklyCredits is display-only, and how ad/referral grants work. This goes beyond the safety profile and provides critical semantics about the data returned.

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 three sentences long, front-loaded with the primary action ('Return the API wallet') followed by essential details on credit semantics. Every sentence earns its place with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description fully explains the return value's semantics and the role of weeklyCredits, which is crucial for correct usage. It does not explicitly mention a common use case like checking credits before a purchase, but the output schema covers the response structure, and the description is sufficiently complete for a read-only tool with simple parameters.

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?

The single parameter include_notes is fully documented in the schema (100% coverage), including its default behavior. The tool description does not add any additional parameter-specific information, so a baseline of 3 is appropriate since the schema already carries the semantic weight.

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 clearly states the tool's function: 'Return the API wallet' and explains the composition of spendable credits. It distinguishes from siblings like manga.buy_credits by focusing on retrieval rather than purchase, making the purpose unambiguous.

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?

The description implies usage for checking available credits but does not explicitly state when to use this tool versus alternatives like manga.buy_credits. There is no direct mention of 'use this to check credits' or exclusions, leaving the agent to infer the appropriate context.

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

All AI Manga & Anime Generator - Mangii MCP 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.