Skip to main content
Glama
noskillish

BankMCP

by noskillish
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create a watch

create_watch

Monitor a bank account for balance thresholds, large debits, or matching transactions, and get notified via webhook when a rule fires.

Instructions

Watch an account in the background and send a notification to the webhook the server's operator configured (NOTIFY_WEBHOOK_URL; Slack or any URL) when a rule fires. The destination cannot be chosen here. Accounts are checked at most 4 times a day, the limit PSD2 sets for unattended access. Rules: balance_below / balance_above: amount threshold on the booked balance. large_debit: any single outgoing payment of at least amount. credit_matching / debit_matching: an incoming / outgoing transaction whose counterparty or description contains match (optionally at least min_amount). credit_missing_by: notify on by_date if no incoming transaction matching match has arrived since the watch was created; also notifies when it does arrive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoShown in the notification, e.g. 'Invoice 2024-17 from Acme'
typeYes
matchNoText to look for in counterparty/description
amountNoThreshold for balance_* and large_debit
accountYesAccount uid or label
by_dateNoDeadline for credit_missing_by
min_amountNoMinimum amount for *_matching and credit_missing_by

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.14
    • removedInput schema / properties / webhook_url
      Removed value: -{
-  "description": "Override the server's NOTIFY_WEBHOOK_URL for this watch",
-  "format": "uri",
-  "type": "string"
-}
  2. First observedv0.1.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It covers key behavioral aspects: the notification destination is fixed (NOTIFY_WEBHOOK_URL, cannot be chosen), checks occur at most 4 times a day (PSD2 limit), and each rule type's exact triggering conditions are detailed (e.g., credit_missing_by notifies on by_date and also when the matching transaction arrives). It does not disclose the response format or error behavior, but the provided details are substantial.

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?

The description is lengthy but each sentence earns its place. It opens with the core purpose, then states key constraints (webhook destination, rate limit), and then systematically explains each rule type with its parameters. It is front-loaded with the primary action and avoids redundancy. While it could be more compact, the detail is necessary given the complexity of six rule types and multiple parameters.

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?

The tool has no output schema, so the description should ideally clarify what the call returns (e.g., a watch ID or confirmation). This is omitted. However, the description fully covers the input semantics, constraints, and rule behaviors, which is the bulk of what an agent needs to invoke the tool correctly. The missing return information is a minor gap, but the overall context is highly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers 86% of parameters with descriptions, but the description adds significant context beyond the schema. For each rule type, it explains how the parameters apply (e.g., 'balance_below / balance_above: amount threshold on the booked balance', 'credit_matching / debit_matching: an incoming / outgoing transaction whose counterparty or description contains match'). This maps parameter meanings to specific rules, going beyond the generic schema descriptions and clarifying optional interactions like min_amount.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's core action: 'Watch an account in the background and send a notification to the webhook... when a rule fires.' It specifies the resource (account), the action (create watch), and the outcome (notification). The enumeration of rule types (balance_below, balance_above, etc.) further clarifies the purpose and distinguishes it from sibling tools like list_watches or delete_watch.

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 when to use the tool (for automated background monitoring) but does not explicitly contrast it with alternatives. It doesn't state 'use this when you need to set up a rule-based alert' or mention that list_watches is for viewing existing watches. The context is clear enough to infer usage, but the description misses direct guidance on when not to use it or when to prefer a sibling.

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