Skip to main content
Glama

Account and quota

account_get
Read-onlyIdempotent

Returns the plan, billing period end, email and SMS quota used and limit, and the send packs available. Free and read only. Check it before a large send. Plan changes and purchases are never done through tools: use billing_portal_link to give the person a link. Requires API key scope: 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": "account_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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 correctly does not restate safety. It does add value the annotations cannot: the required API key scope ("read") and the boundary that billing mutations are out of band. Minor overlap with "read only" but the auth-scope requirement is genuinely new information.

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?

Four short sentences, front-loaded with the return payload before the routing advice. Nearly every clause earns its place, though "Free and read only" partially duplicates readOnlyHint and could be trimmed without loss.

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, the description must convey the return payload, and it does so by enumerating the exact fields. For a zero-parameter, well-annotated read tool, nothing an agent needs to invoke it correctly is missing.

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 for the description to disambiguate; the baseline for zero-param tools applies. The sentence about scope requirement is the closest analogue and is handled under behavioral transparency rather than here.

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 operation and enumerates exactly what is returned: plan, billing period end, email and SMS quota used/limit, and send packs. It also implicitly separates itself from account_update and billing_portal_link by stating that changes and purchases never happen here, so an agent can route correctly without opening another schema.

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

Usage Guidelines5/5

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

Gives an explicit use case ("Check it before a large send") and an explicit exclusion with the alternative named ("Plan changes and purchases are never done through tools: use billing_portal_link"). Both the when and the when-not are stated, with the redirect target identified.

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