Skip to main content
Glama
Sign In
sparebank1-mcp

sparebank1-mcp

by MrLightful
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get account

sb1_get_account
Read-onlyIdempotent

Retrieve details for an ordinary bank account by supplying its exact account key. Use this endpoint only for standard accounts; credit-card and pension keys are not supported.

Instructions

Get an ordinary account using its exact bank account key. Credit-card and pension keys are not supported by this endpoint.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountKey": "<accountKey>"
    },
    "name": "sb1_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountKeyYes

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuine behavioral value beyond that by disclosing a failure mode: certain key types are rejected by this endpoint. It does not discuss auth, rate limits, or response shape, but the output schema covers the latter.

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?

Two tight sentences with the positive constraint first and the exclusion second. Nothing is wasted and nothing important is buried.

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?

For a one-parameter read tool with rich annotations and an output schema, the description covers the essential selection constraint and the main caveat. The only meaningful gap is not pointing to where account keys come from, which matters for a tool keyed on an exact identifier.

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 0% for the single parameter, so the description must compensate. It does partially, by specifying that the key must be an exact ordinary bank-account key and ruling out credit-card and pension keys, but it never says where to obtain such a key (the sibling sb1_get_account_keys) or what its format looks like beyond the regex in the schema.

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?

Specific verb+resource ("Get an ordinary account") with a scoping qualifier that separates it from credit-card and pension lookups. It does not, however, distinguish itself from the closely named sibling sb1_get_account_details, so the agent still has to guess between those two.

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?

"Using its exact bank account key" plus the exclusion "Credit-card and pension keys are not supported" gives clear when-to-use and when-not-to-use context. It stops short of naming an alternative endpoint for those unsupported key types, so the agent is left to search siblings.

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