Skip to main content
Glama

get_accounts

Read-only

List all user accounts with current balances. Returns account name, type, currency, current balance (in original and base currency), and credit limit.

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

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by account type (e.g., "checking", "savings", "credit_card")
includeExcludedFromStatsNoInclude accounts excluded from stats. Default: false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already declares the safe-read profile, so the description only needs to add context. It does add value by enumerating what comes back (name, type, currency, dual-currency balance, credit limit), but says nothing about ordering, pagination, or how excluded-from-stats accounts are treated in the default response.

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 short sentences, front-loaded with purpose and followed by return contents. No filler or repetition; the only missed opportunity is not folding the sibling differentiation into the same tight space.

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?

There is no output schema, so the explicit list of returned fields is genuinely necessary and is provided. For a two-optional-parameter read tool with a readOnlyHint annotation, the remaining gaps are minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both the type filter and includeExcludedFromStats are already documented with an explicit default. The description adds no parameter meaning beyond that, which is acceptable given full schema coverage but earns only the baseline.

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 ("List") and resource ("user accounts") plus the scope ("current balances"). It does not distinguish itself from the sibling get_account (singular) or get_total_balance, so an agent must infer the plural-vs-single split rather than being told.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance at all. With get_account, get_total_balance, and get_net_worth_history as siblings, the description never states that this is the bulk-list variant versus the single-account fetch, leaving routing entirely to inference from the tool name.

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.