Skip to main content
Glama

Get the account

get_account
Read-onlyIdempotent

Who you are signed in as, the organization (workspace) and its credit balance Returns the organization the credentials act for (the workspace, as the app calls it; type artist holds one artist, label a roster, creator projects), how they authenticate and their scopes, the credit balance (available, monthly, top-ups) and its plan, if any: active says whether it lets the workspace create (without an active plan, creating answers 402 plan_required), storage (used_bytes against limit_bytes: an upload or new video that does not fit answers 402 storage_full, and deleting videos or archiving songs frees space at once), where it is billed, when the period ends, and a downgrade or interval switch waiting for the renewal as scheduled_change. Without a plan, free_song says where the person's one free song stands (signed in as them, never with an API key, where it is null, as it is with a plan): available (upload one song now, with create_song; it plays in the Looks), unverified (they confirm their email first), used (its song_id and title, and video: available true while its one free video is still to make, video_id once it is) or taken (it went to another workspace or account). The free video is a lyric video of the free song with an existing Look (look.mode existing) in one aspect ratio, of at most 60 seconds of it (a trim: a part of a longer song), quoted and created as usual: it holds no credits; anything else answers 402 plan_required. Monthly credits reset every month; top-ups never expire. On the organization, image_url is the picture uploaded for it (null without one); while it has none, image_fallback is the cover of its newest song still there that has one (song_id, preview_url 640 px and thumbnail_url 160 px WebP), to show in its place, or null without such a song. It is read-only, never saved as the picture, and follows the newest song (a new song or an archived one changes it). Check it before creating anything.

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

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 readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds substantial context beyond that: what an inactive plan means for creates (402 plan_required), what used_bytes against limit_bytes triggers (402 storage_full) and that deletion frees space immediately, that monthly credits reset while top-ups never expire, and that image_fallback is read-only, never persisted, and tracks the newest song. Remaining gap: no mention of rate limits or response shape/ordering.

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

Conciseness2/5

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

It is one long run-on paragraph with heavily nested parentheticals that must be unpacked mid-sentence, which hurts scanability even though the leading clause is well front-loaded. Much of the free-song and image_fallback detail is verbose specification prose rather than selection-critical guidance, so several sentences do not earn their place for an agent deciding whether to call.

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?

With no output schema, no parameters and a broad return payload, the description carries the full burden and does so: it enumerates the organization fields, plan/credit structure, storage figures and the free_song state machine with its four states. An agent knows what it will receive and what each state implies before calling.

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 there is no parameter semantics for the description to add; the schema does not need compensating for. Baseline 4 is the appropriate ceiling 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?

The opening states specific resources: the signed-in identity, the organization/workspace, its authentication scopes and credit balance. That is far more concrete than a restated title, and no sibling covers the same ground (get_artist, get_song, get_options are all narrower). It stops short of naming a sibling it is not, so 4 rather than 5.

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 gives a clear operative instruction, "Check it before creating anything," and explains the concrete consequence of skipping it (402 plan_required or 402 storage_full on create). It does not name alternative tools for balance or plan questions, so no explicit when-not guidance or alternative routing.

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