Skip to main content
Glama

Get your account

get_account
Read-only

Returns the connected account's email, its own plan name if it has one, its credit balance and how many starter downloads and site checks are left today. Read-only. Needs a connected account.

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

Output Schema

NameRequiredDescriptionDefault
planYes
emailYes
todayYes
creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so "Read-only" is largely redundant. The genuinely additive piece is the authentication prerequisite ("Needs a connected account"), which tells the agent the call will fail without a linked account — the kind of context the annotations do not cover. It stops short of describing the failure mode or any rate/refresh behavior.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the returned data before the safety and precondition notes. Every clause carries information; the only near-waste is restating "Read-only" alongside an annotation that already says so.

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?

With an output schema present and zero inputs, the description need only support selection and preconditions, which it does. The one gap is behavior when the precondition fails — nothing says whether an unconnected account yields an error or nulls — but that is minor for such a simple read.

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 nothing for the description to disambiguate; baseline 4 applies. The description correctly never invents inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb+resource ("Returns the connected account's...") and enumerates exactly what comes back: email, plan name, credit balance, remaining starter downloads and site checks. No sibling (get_design, get_footage, get_job, check_site) could be confused with this account-level read.

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 stated precondition "Needs a connected account" tells the agent when the call is viable, but there is no explicit when-to-use-vs-alternatives guidance (e.g. use get_starter versus this for starter-quota detail). Usage is inferable but not directed.

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.