MascotLab

Account and credits

get_account

Read-onlyIdempotent

Credit balance, whether the account has ever bought credits (which is what unlocks animation), and what each generation costs (mascot 2, prop 2, pose 2, animation 5 credits). Call this before expensive work to know what the balance allows.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ok`	Yes
`frozen`	No
`credits`	Yes
`purchased`	Yes
`billing_hint`	No
`credit_costs`	No
`animation_requires_purchase`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 23, 2026

addedOutput schema / properties / animation_requires_purchase
```
Added value: +{
+  "type": "boolean"
+}
```
removedOutput schema / properties / animation_requires_subscription
```
Removed value: -{
-  "type": "boolean"
-}
```
addedOutput schema / properties / purchased
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / subscription

Removed value: -{
-  "type": [
-    "object",
-    "null"
-  ]
-}

changedOutput schema / required

Previous value: -[
-  "ok",
-  "credits"
-]New value: +[
+  "ok",
+  "credits",
+  "purchased"
+]

First observedAug 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description adds real domain behavior beyond that: a prior credit purchase is the gate that unlocks animation, and it exposes the credit price of each generation type — non-obvious business rules an agent cannot get from the schema.

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?

A single sentence that front-loads the three returned facts and parenthesizes the unlock rule, then closes with the operational reason to call it. No filler, no repetition of schema or annotation content.

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?

For a no-arg, read-only status tool with an output schema already defined, the description covers everything needed: what is returned, the gating rule for animation, and the cost model. Nothing required for correct invocation is missing.

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?

Zero parameters, so there is nothing to disambiguate; baseline 4 applies. The description correctly implies no arguments are needed, consistent with an empty properties object.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates exactly what the tool returns: credit balance, whether the account has ever purchased credits, and the per-generation cost table (mascot 2, prop 2, pose 2, animation 5). That grounds it clearly against generation siblings like create_animation/create_mascot, though it never explicitly says 'this is a read-only account-info call, not a generation action.'

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?

'Call this before expensive work to know what the balance allows' gives an explicit invocation condition tied to the costly sibling tools. There is no stated when-not or alternative (e.g. no other balance-checking tool exists), but the positive guidance is concrete.

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

All MascotLab 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?