Skip to main content
Glama
Sign In
sparebank1-mcp

sparebank1-mcp

by MrLightful
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List transactions

sb1_list_transactions
Read-onlyIdempotent

Retrieve bounded transactions for one or more account keys, optionally filtered by date and classified categories, while retaining bank errors and truncation notices.

Instructions

Get bounded transactions for one or more account keys, optionally classified. Retains bank errors and reports possible truncation. No cursor is documented. Dates use Europe/Oslo.

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": {
      "accountKeys": "<accountKeys>"
    },
    "name": "sb1_list_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNo
toDateNoInclusive date in Europe/Oslo, YYYY-MM-DD.
fromDateNoInclusive date in Europe/Oslo, YYYY-MM-DD.
rowLimitNoBank row limit. No offset or cursor is documented. Narrow date windows if capped.
classifiedNoInclude bank-provided categories, subscriptions and recurring flags.
accountKeysYesExact account keys returned by sb1_list_accounts.
enrichWithMerchantLogoNoOnly available for classified transactions; can increase latency.

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and idempotent safety. The description goes beyond them usefully: it discloses that bank errors are retained, that truncation may occur and is reported, and that no cursor exists, which directly shapes query strategy. It does not explain the shape of the truncation signal, which is why it is not a 5.

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?

Four short sentences, front-loaded with the core operation before the caveats. Every sentence carries a distinct fact; nothing is redundant or padded.

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?

An output schema exists, so return-value explanation is not required, and annotations carry the safety profile. For a 7-parameter read tool, the description covers purpose, pagination limits, error retention, and timezone; only the precise meaning of 'bounded' and how truncation is signalled remain unspecified.

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 coverage is 86%, so the schema already documents the date format, the Europe/Oslo timezone, the rowLimit cap, and the classified flag. The description restates the timezone and cursor absence rather than adding new parameter meaning, so the baseline 3 is correct.

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?

States a specific verb and resource (get transactions) with scope qualifiers: bounded, one or more account keys, optionally classified. It reads clearly against list/export/detail siblings, though it never names them explicitly to sharpen the boundary.

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?

Implies when the tool fits (bounded windows, no cursor) but gives no explicit when-not guidance or named alternatives. An agent must infer from sibling names that sb1_get_transaction_details or sb1_export_transactions exist for other purposes.

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