Skip to main content
Glama

Car Background AI

Get credit balance

get_credits
Read-only

Read the workspace's current credit balance, returned as balance. One credit is one photo from generate_background or one preview from create_background or refine_background; hide_license_plates uses none. Call it before a batch to check there are enough credits, or after an insufficient-credits error. Read-only and free; takes no parameters. It does not show plans or prices: when the balance is too low, use list_plans, then create_checkout (no subscription yet) or change_plan (existing subscription).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare it read-only, non-destructive, and closed-world, so the baseline is low. Beyond that, the description adds what the annotations do not: the call is free, takes no parameters, and the credit unit maps to specific actions (one credit equals one photo from generate_background, one preview from create_background or refine_background, and hide_license_plates uses none), which is genuinely useful context for planning. It says nothing about how current the balance is or about eventual consistency, so it falls short of a 5.

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?

Four tight sentences, front-loaded with what is returned, then cost semantics, then when to call, then what it is not for. Every sentence carries information the agent needs, and none repeats the annotations verbatim.

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?

There is no output schema, but the description names the returned field (`balance`), explains the unit of account, and covers the error-recovery path. For a zero-parameter, read-only tool, nothing an agent needs in order to call it or to act on the result 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?

There are zero parameters and 100% schema coverage, so the baseline is 4. The description confirms "takes no parameters," which is consistent with the empty schema but adds no further meaning, as there is none to add.

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 opens with a specific verb and resource ("Read the workspace's current credit balance") and names the returned field, `balance`, so the agent knows exactly what it gets. It also distinguishes the tool from nearby siblings by stating it does not show plans or prices, pointing to list_plans/create_checkout/change_plan instead.

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 triggers for calling: before a batch to verify credits, or after an insufficient-credits error. It also gives concrete routing for the failure case (list_plans, then create_checkout if there is no subscription or change_plan if there is), so the agent does not have to infer which sibling to use.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources