Skip to main content
Glama
Sign In
sparebank1-mcp

sparebank1-mcp

by MrLightful
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Export booked transactions

sb1_export_transactions
Read-onlyIdempotent

Exports raw transaction CSV for one account and date range, with optional field selection; neutralize spreadsheet formulas before opening.

Instructions

Return raw UTF-8 bank CSV for one account and date window. CSV cells are untrusted; neutralize formulas before opening in spreadsheets. Optional field follows the bank’s documented single-field schema.

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>",
      "fromDate": "<fromDate>",
      "toDate": "<toDate>"
    },
    "name": "sb1_export_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldNo
toDateYes
fromDateYes
accountKeyYes

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the description wisely spends its words elsewhere: it discloses the output medium (raw UTF-8 CSV), the security property that cells are untrusted and need formula neutralization, and that only one optional column can be selected. It does not mention size limits or pagination behavior, which keeps it off 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?

Three short sentences, front-loaded with what is returned and where, with the security warning before the param note. The final sentence about the 'documented single-field schema' is compressed to the point of being unhelpful, but nothing is padding.

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 need not be re-explained, and the safety profile is in annotations. What is missing for a 4-parameter export tool with 0% schema coverage is date-window semantics and any note on export size/limits.

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 the description only gestures at one of four parameters ('Optional field follows the bank's documented single-field schema'), which is opaque rather than explanatory. accountKey, fromDate and toDate get no meaning added — no statement of whether the date window is inclusive, whether toDate is exclusive, or what form the accountKey takes beyond its regex.

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 ('Return raw UTF-8 bank CSV') plus scope ('one account and date window'), which separates it from sb1_list_transactions, the obvious sibling. The distinction is conveyed by 'raw CSV' rather than an explicit contrast, so it stops short of a 5.

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 one-account/one-date-window constraint implies when the tool applies, and the 'one account' note hints you can't bulk-export. But it never names sb1_list_transactions or sb1_get_transaction_details as the alternative for structured/single-record reads, and gives no when-not guidance.

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