Skip to main content
Glama

Show the connected account

get_account
Read-only

Shows which account this connection acts as (personal or an organization, and the role), its plan, credits used, balance, and what each tool costs it. Free.

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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds that the call is free (no credit consumption) and scopes the result to "this connection" rather than an arbitrary account. The per-tool cost disclosure is meaningful behavior an agent would not otherwise know. It does not say whether results are cached or rate-limited, so not a 5.

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 front-loaded sentence that puts the core purpose first and then lists the return payload, plus a one-word cost signal. Every clause carries information given there is no output schema. The dense parenthetical is slightly compressed but still readable.

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 no output schema and no parameters, the description carries the burden of explaining returns, and it does so concretely (account type, role, plan, credits, balance, per-tool costs). Combined with readOnlyHint, an agent has enough to call it correctly. Minor gap: it does not indicate what happens if the connection is unauthenticated or what shape the per-tool cost data takes.

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 at the schema level. Baseline for a parameterless tool is 4. The description correctly does not waste words on inputs.

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?

States a specific verb and resource ("Shows which account this connection acts as") and enumerates the payload: account type, role, plan, credits used, balance, and per-tool costs. An agent can distinguish this identity/billing-summary tool from the verification and checkout siblings. It stops short of naming any sibling it should be preferred over, so it is not 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 Guidelines3/5

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

Usage is implied rather than stated: an agent can infer it is the tool to call when it needs to know the acting identity, credit balance, or per-tool pricing. There is no explicit when-to-use/when-not framing and no reference to alternatives such as get_billing_portal_link for payment flows. "Free" hints that calling it is a no-cost sanity check, which is mild guidance.

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