Skip to main content
Glama

Rigged Clean

get_account

Read-only

Read the credit balance, preview allowance and prices. With a pack and bearer key, return a checkout link for a person to open and approve payment.

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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
packNo
anonymous_sessionNoKeyless session credential. Save the value returned on your first call and pass it on related calls and retries.

Output Schema

NameRequiredDescriptionDefault
limitsYes
pricingYes
held_usdYes
balance_usdYes
checkout_urlNo
available_usdYes
free_uses_leftYes
held_micro_usdYes
anonymous_sessionNoKeyless session credential. Save the value returned on your first call and pass it on related calls and retries.
balance_micro_usdYes
available_micro_usdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's added value is the auth/flow context: a bearer key plus a pack is required for checkout, and a human must open and approve the payment link. That is useful, but it omits whether link generation is idempotent, whether it expires, and how credit/price values are denominated or scoped.

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?

Two tight sentences, with the primary read behavior front-loaded and the conditional checkout path second. Nearly every word earns its place, though 'preview allowance' reads as jargon compression rather than precision.

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

Completeness3/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-shape explanation is unnecessary, and the tool itself is low-complexity with two optional params. Still, the split between the read path and the checkout-link path is only half-specified, and the enum tiers are left undefined.

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?

Schema coverage is 50%: anonymous_session is fully documented in the schema, but the pack enum values p5/p20/p100 carry no schema description. The description adds that pack triggers the checkout-link path but never explains what the tiers mean, so it only partly compensates for the coverage gap.

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?

Names a concrete verb set and resource: read credit balance, allowance, prices, and return a checkout link. An agent can tell this is the account/billing-read tool, distinct from get_job, create_upload, and enhance_media, though phrasing like 'preview allowance' stays slightly vague.

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 second sentence gives one real conditional: supplying a pack together with a bearer key switches the behavior to returning a checkout link. It does not say what the no-pack default returns, nor when the checkout path is preferred over simply reading prices, so usage is implied rather than spelled out.

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