Skip to main content
Glama

Account

account

get returns balance, pricingUrl, and defaultImageModelId (the model a quote uses when imageModelId is omitted). settings.defaultImageModelId is only a saved override and is null when that default applies. billing returns usage, orders, and invoices. update_settings changes defaults. Buy tokens at /pricing. Image generation spends the website token balance. Purchases happen at /pricing; this tool never takes payment.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false but destructiveHint=false and openWorldHint=false; the description adds genuinely useful context beyond them: image generation consumes the token balance, and money movement is out of scope entirely. It does not disclose whether update_settings requires elevated permissions, whether cleared values (empty string / null) reset overrides, or whether the call is reversible, which matters for the one mutating branch.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with the highest-value fact (what get returns), but the pricing information is stated twice — 'Buy tokens at /pricing' and 'Purchases happen at /pricing; this tool never takes payment' — wasting a sentence in an already terse paragraph. The mid-paragraph jump from return values to purchase routing also breaks the get/billing/update_settings structure it establishes.

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?

There is no output schema, so the description correctly takes on the burden of describing return contents for get and billing. For a three-branch discriminating-union tool it covers each branch, leaving only the mutation side effects and reset semantics of update_settings unaddressed.

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?

With 100% schema coverage the baseline is 3, and the description earns above it by explaining the non-obvious distinction between the top-level defaultImageModelId (what a quote falls back to when imageModelId is omitted) and settings.defaultImageModelId (a saved override that is null when the default applies). The op values are also characterized by their effect rather than just enumerated. It stops short of explaining what the empty-string or null values mean for defaultAgeRange/preferredLocale clearing.

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 decomposes the ambiguous top-level name 'account' into three concrete operations and states what each returns or changes: 'get returns balance, pricingUrl, and defaultImageModelId', 'billing returns usage, orders, and invoices', 'update_settings changes defaults'. An agent can tell which op it needs without opening the schema, though the umbrella purpose (account settings and billing) is only implied by the name rather than stated in a lead sentence.

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?

It maps intent to op: balance/quotas via get, usage/orders/invoices via billing, changing defaults via update_settings, and it explicitly excludes payments ('Buy tokens at /pricing ... this tool never takes payment'). What is missing is any guidance on prerequisites or ordering, and no sibling tool is named as the alternative for the excluded payment action.

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