agentee-mcp

Check Studio credits

get_studio_credits

Read-onlyIdempotent

Check the account owner's Studio credit balance before generating a custom print to show the 1-credit cost and remaining credits; new accounts start at 0 until first generation adds 20 credits.

Instructions

Return the account owner's Studio credit balance; reading it spends nothing. Check it before generate_custom_print so you can tell the human the cost (1 credit per generation with either engine; preserve=true is free) and what will be left. No Studio account yet → balance 0 and studio_account=false; the first generation creates the account with 20 welcome credits. Every bought tee adds 20 credits, and more can be bought at allover.art/studio.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`note`	No
`error`	No
`detail`	No
`balance`	No	Current Studio credit balance.
`studio_account`	No	False if the user has no Studio account yet (first generate auto-creates one).

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.0Oct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that reading spends nothing, that a missing Studio account returns balance 0 with studio_account=false, that first generation creates the account with 20 welcome credits, and how credits accrue from tee purchases. These are rich behavioral details not inferable from the annotations alone.

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 front-loaded with the core balance-check purpose and the fact that reading is free. It remains efficient overall, though the final sentence about buying more credits at allover.art/studio is slightly more promotional than strictly necessary for invoking the tool.

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?

An output schema exists, so return values need not be explained in detail. The annotations cover the safety profile, and the description adds the key account-state and cost context an agent needs to call 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?

This tool has zero parameters, so there are no parameter semantics to document. The baseline score for a zero-parameter tool is 4, and there is nothing in the description that needs to compensate for an input-schema gap.

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: return the account owner's Studio credit balance. It also clearly distinguishes this read-only balance check from the generation action it supports, so an agent can identify the tool's job immediately.

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 explicitly says to check this before generate_custom_print so the human can be told the cost and remaining balance. It also explains the no-account case and the free preserve=true case, giving clear conditions for when and how to use the result.

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