Skip to main content
Glama

Get account

get_account
Read-only

The account's plan and how many videos it has left (credits.available).

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

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the annotation carries the safety burden. Beyond that, the description only supplies the returned field 'credits.available', with no mention of whether the account lookup is cached, requires authentication, or what an exhausted credit balance looks like. Useful, but thin on behavior for a zero-annotation-detail tool.

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?

A single compact sentence with no filler; the concrete field reference is placed immediately after the plain-language summary. It is a noun-phrase fragment rather than a full sentence, which slightly weakens front-loading of the action, but nothing is superfluous.

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?

With no output schema, the description is the only documentation of the return value, and it covers just two things: plan and credits.available. That is enough for an agent to know the gist but not the shape of the response or how to interpret an empty/zero-credit account. Adequate minimum for a simple read tool, not complete.

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 schema has zero parameters at 100% coverage, so there is nothing for the description to disambiguate; baseline of 4 applies. The description correctly does not waste words inventing parameter details for a no-arg call.

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 names the specific resource content being fetched: the account's plan and its remaining video allowance, including the exact field 'credits.available'. That is enough to distinguish it from the video-oriented siblings (create_video, get_video, list_videos, revise_video, share_video), which operate on individual videos rather than account-level state. It stops short of a full verb+resource statement but the object is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this tool or why: nothing like 'call before create_video to verify remaining credits'. The named return values hint at a credit-check use case, but the agent must infer it entirely. No exclusions or alternatives are mentioned, though in fairness no sibling covers account data.

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.