Skip to main content
Glama
sparebank1-mcp

sparebank1-mcp

by MrLightful

Get account balance

sb1_get_account_balance
Read-onlyIdempotent

Retrieves the current balance for a specified account number via a read-only bank endpoint, enabling balance checks without initiating transactions.

Instructions

Read the current balance by account number. Uses the bank’s read-only POST 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": {
      "accountNumber": "<accountNumber>"
    },
    "name": "sb1_get_account_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNumberYes

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.4/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. The description adds useful context that the bank endpoint is a read-only POST endpoint, which prevents an agent from mistaking POST for a mutation, but it does not mention authentication needs, rate limits, or error behavior.

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 short sentences with no wasted text. The purpose is front-loaded and the endpoint caveat follows immediately.

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 simple read operation with an output schema and annotations covering safety and idempotence, the description is largely complete. It discloses the distinct read-only POST endpoint behavior, though it omits authentication or prerequisite context that could matter for a banking API.

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%, so the description should compensate for the single parameter, but it only says 'by account number' without specifying the required 11-digit format or any validation behavior. The schema itself contains the pattern, but the description adds little meaning beyond the property name.

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 states a specific verb and resource: reading the current balance by account number. It is clear enough to distinguish from siblings like get_account_details or list_transactions, though it does not explicitly name alternatives.

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

Usage Guidelines3/5

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

The description implies the tool is used when a current balance is needed, but it does not say when to use it versus sibling tools such as get_account_details or list_transactions. No exclusions or prerequisites are provided.

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