Skip to main content
Glama

Plaid Get Balance

plaid_get_balance
Read-onlyIdempotent

Get real-time account balances for linked accounts. Returns current, available, and limit balances. Example: get_balance({ access_token: "access-sandbox-xxx", _apiKey: "client_id:secret" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_apiKey": "your-plaid-api-key",
      "access_token": "access-sandbox-abc123def456"
    },
    "name": "plaid_get_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesPlaid credentials as "client_id:secret"
access_tokenYesPlaid access token for the linked institution

Output Schema

NameRequiredDescriptionDefault
itemNoItem metadata
accountsNoList of accounts with current balance information
request_idNoUnique request identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is carried by structured data. The description adds that balances are 'real-time' and enumerates the balance types returned, but says nothing about auth failure modes (e.g. expired access tokens), rate limits, or what happens for accounts with no limit value.

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?

The purpose and return values are front-loaded in two short sentences, and the trailing example is compact. The example is largely redundant with the schema's own example field, which is the only wasted space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not explain return values at all, and annotations cover the safety profile. The remaining gap is operational: no mention of credential/auth failure behavior, which matters for an open-world third-party integration tool.

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% and both required parameters (_apiKey as client_id:secret, access_token) are documented in the schema. The description's inline example merely restates the schema example and adds no new meaning about parameter semantics.

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 ('Get real-time account balances for linked accounts') and names the returned fields (current, available, limit). It is clear enough to separate from plaid_get_accounts, but the description never explicitly contrasts the two, so it stops short of full sibling differentiation.

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?

There is no when-to-use guidance, no condition naming an alternative such as plaid_get_accounts, and no prerequisites or exclusions. Usage is only implied by the tool name and the example invocation.

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.