Skip to main content
Glama

Account, plan and balance

get_account
Read-onlyIdempotent

The signed-in catchy-me account: name, email, language, plan («тариф»: code, status, period end), briefs («брифы») left this period and when they renew, the free brief, the balance in whole credits (available = balance minus holds of running work) and the search limits (max leads per search). Call it first to know what the user can do: starting a search or an outreach needs a plan or credits, and each new setup spends one brief. [REST: GET /api/account, GET /api/config]

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

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavior beyond that: available credits are balance minus holds of running work, brief consumption is a side effect of new setups, and the call fans out to two REST endpoints (GET /api/account, GET /api/config). It does not mention auth/permission requirements beyond "signed-in".

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?

It is front-loaded with the resource and then lists returned fields in a single dense sentence; almost every clause carries information. The parenthetical bilingual glosses («тариф», «брифы») and the bracketed REST note add length that a purely agent-facing reader does not strictly need, costing it a 5.

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 and no parameters, the description carries the full burden of describing the response, and it does so field by field, including the derived "available" credit definition. An agent can call this correctly with no further information.

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 no parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies a no-argument snapshot call rather than suggesting any filtering or scoping options.

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 exact resource and enumerates its contents (name, email, language, plan with code/status/period end, briefs, free brief, balance, search limits), so an agent knows precisely what comes back. It does not explicitly distinguish itself from near-siblings like get_subscription or get_balance_history, which keeps it short of a 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?

"Call it first to know what the user can do" gives clear ordering guidance, and the follow-on explains why: searching or outreach requires a plan or credits, and each new setup consumes one brief. It stops short of naming alternatives or exclusions (e.g., when to prefer get_subscription or get_balance_history instead).

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