Skip to main content
Glama

Check Muro credits

get_credits
Read-only

Paid tools only. Show the Muro credit balance and plan of the connected account. Painting costs 1 credit per colour in Standard, 2 in HD and 3 in Ultra.

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read profile is covered. The description adds genuinely useful behavior beyond that: the account must be paid/connected, and painting consumes credits at tiered rates (1/2/3 per colour for Standard/HD/Ultra), which tells an agent how the returned number relates to future actions. It stops short of stating behavior for unauthenticated or free-tier accounts.

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?

Three short sentences with zero filler: eligibility gate first, then the returned values, then the cost model that makes the returned number actionable. Every sentence earns its place and the key output is front-loaded.

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?

With no parameters, no output schema, and read-only annotations, this is a simple tool and the description covers the essentials: what is returned (balance and plan), who can call it (paid accounts), and how credits are consumed. The only minor gap is the absence of failure-mode behavior for insufficient balance or an unpaid plan.

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?

The tool takes zero parameters, so the baseline is 4 and the schema has nothing to document. The description correctly implies the account is derived from the connection context rather than passed in, which is the only parameter-related nuance that exists here.

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?

"Show the Muro credit balance and plan of the connected account" gives a concrete verb (show/read) and two named resources (credit balance, plan). It is unambiguous about what the tool returns, though it does not explicitly note that no sibling tool overlaps with this read (the siblings listed are painting/visualization tools, so differentiation is largely unnecessary).

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?

"Paid tools only" plus the per-colour pricing implies you should check credits before spending them on painting, and that this tool is gated to paid accounts. However, the when-to-use condition is only implied — there is no explicit instruction such as "call this before paint operations to confirm sufficient balance," and no statement of what to do if the account is unpaid.

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