Skip to main content
Glama
s-c-h-a-f-e-r

n26-mcp

by s-c-h-a-f-e-r
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get balances

get_balances
Read-onlyIdempotent

Retrieve read-only balances for consented accounts, showing amount, currency, and reference date. View balance details without payment actions, restricted to the account owner.

Instructions

Read-only balances for the consented accounts.

Shows balance type, amount, currency and reference date. There is no payment action. Show the result only to the account owner.

Input Schema

NameRequiredDescriptionDefault
accountNoAccount uid from list_accounts. Omit for every consented account.

Output Schema

NameRequiredDescriptionDefault
accountsYes
owner_onlyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint), it provides crucial behavioral context regarding data fields returned (type, amount, currency, date) and a necessary authorization constraint (only shown to the account owner).

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 description is brief and front-loaded, though the second sentence slightly over-explains the basic data structure that is often inferred from an output schema.

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?

It is extremely complete for a read-only, scoped query. It defines the boundaries (consented accounts), the scope of the result (owner only), and the data included (fields).

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?

Since schema coverage is 100%, the description adds value by reinforcing the meaning of the 'account' parameter—that omitting it retrieves balances for all consented accounts, which is the core functionality.

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 clearly identifies the resource (balances) and the action (read-only), distinguishing it from siblings like list_accounts by specifying the operational scope.

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

Usage Guidelines4/5

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

It guides usage by explaining that the results are tied to consented accounts, and explicitly notes that no payment action is possible, helping the agent avoid misuse.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools