Skip to main content
Glama
Sign In
sparebank1-mcp

sparebank1-mcp

by MrLightful
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List accounts

sb1_list_accounts
Read-onlyIdempotent

List accessible accounts with balances, currencies, ownership, and transfer permissions; optionally include Ask, BSU, NOK, pension, currency, or credit-card accounts. Credit cards may fail silently.

Instructions

List accessible accounts, balances, currencies, ownership and transfer permissions. Credit-card retrieval can fail silently at the bank.

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": "sb1_list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeAskAccountsNo
includeBsuAccountsNo
includeNokAccountsNo
includePensionAccountsNo
includeCurrencyAccountsNo
includeCreditCardAccountsNo

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description does not need to repeat those traits. It adds useful behavioral context by warning that credit-card retrieval can fail silently at the bank, which is valuable beyond the annotations. It does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no wasted wording. The core purpose is front-loaded, and the credit-card caveat is a relevant second sentence.

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, and the annotations cover safety traits. However, with six parameters at 0% schema description coverage, the definition is incomplete regarding how the include flags affect the result. It is minimally adequate but leaves meaningful invocation details unstated.

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

Parameters2/5

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

Schema description coverage is 0% and there are six optional boolean parameters, but the description does not explain includeAskAccounts, includeBsuAccounts, includeNokAccounts, includePensionAccounts, includeCurrencyAccounts, or includeCreditCardAccounts. It hints at currencies and credit-card retrieval, but it does not map those concepts to the parameters or explain what happens when flags are omitted.

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?

The description uses a specific verb and resource: 'List accessible accounts', and it names the returned data such as balances, currencies, ownership, and transfer permissions. It is clear what the tool does, but it does not distinguish itself from siblings such as sb1_list_child_accounts or sb1_get_account.

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?

The description gives no explicit guidance on when to use this tool versus alternatives, and it does not mention prerequisites or exclusions. The agent can infer that it is for listing accounts, but there is no routing help among the many sibling account tools.

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