Skip to main content
Glama
sparebank1-mcp

sparebank1-mcp

by MrLightful

Get account details

sb1_get_account_details
Read-onlyIdempotent

Retrieve detailed account information such as interest rates, withdrawal limits, blocked amounts, and other account specifics using an account key.

Instructions

Read interest rates, withdrawal limits, blocked amounts and additional account details.

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_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountKeyYes

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description's contribution is the enumeration of returned data, which is mildly useful context but discloses nothing about access requirements (openWorldHint=true suggests external service, and the description never mentions auth or connectivity prerequisites).

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?

A single efficient sentence that front-loads the verb and the most notable returned fields. Nothing is wasted, though the trailing 'additional account details' is vague filler that could have carried the sibling-differentiation instead.

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 return values needn't be explained in prose, and the read-only annotations carry the safety burden. The remaining gaps are the undocumented accountKey parameter and the absence of any routing guidance among the many sb1_get_* siblings, which the description does not address.

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%: accountKey is documented only by a regex pattern and length bounds, with no explanation of its meaning, format, or where to obtain one. The description never mentions the parameter at all, so it does not compensate for the coverage gap, leaving the agent to guess whether this is a child account key, a parent key, or an opaque ID.

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 ('Read') plus an enumerated set of resources (interest rates, withdrawal limits, blocked amounts, additional details), so the agent knows what it returns. However, it does not distinguish itself from close siblings such as sb1_get_account or sb1_get_account_balance, which appear equally plausible for the same intent.

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 statement of when to use this versus sb1_get_account, sb1_get_account_balance, or sb1_get_account_keys. The agent must infer selection purely from the returned-fields list.

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