Skip to main content
Glama

get_account_summary

Read-onlyIdempotent

Read your credit balance (free and purchased, with the next expiry), Question Bank access, and Unlimited plan status (the plan runs interviews on your own Gemini API key; it is reported as geminiByok). Read-only: never changes billing and never returns payment details or keys. Requires account:read.

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
creditsYes
geminiByokNo
websiteUrlYes
questionBankYes

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 cover readOnly, idempotent, non-destructive, and closed-world, so the description's added value is the explicit guarantee that it never changes billing and never returns payment details or API keys — important security context for an account-facing tool. It also explains the geminiByok naming convention, which is behavior an agent could not infer from structured fields.

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?

Two sentences, front-loaded with the returned data and followed by safety guarantees and the required scope. The parenthetical about Gemini BYOK is slightly dense but earns its place by pre-empting confusion over the field name.

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, the description does not need to explain return values, and it still covers the auth requirement and the negative guarantees. It is close to complete for a zero-parameter read tool, with only minor room to note anything about failure modes or freshness of balance data.

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 meaning to add and the baseline of 4 applies. The description correctly refrains from inventing inputs and instead spends its words on output semantics.

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?

The description uses a specific verb ('Read') and enumerates the exact resources returned: credit balance (free and purchased with next expiry), Question Bank access, and Unlimited plan status. It even disambiguates the ambiguous field name by stating the plan is reported as 'geminiByok', which separates it cleanly from siblings like get_progress_summary or get_account billing-adjacent tools.

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 scope (billing/entitlement status) implies when to call it, and 'Requires account:read' states a prerequisite. However, there is no explicit when-to-use versus when-not-to-use guidance and no named alternative for related reads such as get_progress_summary, leaving the agent to infer 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