Skip to main content
Glama
starling-bank-mcp

starling-bank-mcp

by domdomegg

Withdraw from savings goal

savings_goal_withdraw

Withdraw funds from a Starling Bank savings goal. Provide the account UID, goal UID, and amount to move money out of that goal.

Instructions

Withdraw money from a savings goal

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": {
      "accountUid": "<accountUid>",
      "savingsGoalUid": "<savingsGoalUid>",
      "amount": "<amount>"
    },
    "name": "savings_goal_withdraw"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes
accountUidYesThe account UID
savingsGoalUidYesThe savings goal UID

Output Schema

NameRequiredDescriptionDefault
successNo
transferUidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

C2.3/5.0
Behavior2/5

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

The only annotation is readOnlyHint=false, which already indicates a mutation. The description adds no behavioral context such as reversibility, permissions required, side effects on the savings goal balance, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is concise and front-loaded, but it is under-specified for a financial mutation with a nested amount object. It earns its place but does not provide sufficient structure or detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool is a mutation with a nested amount object and only a readOnlyHint=false annotation, the description is incomplete. It does not explain prerequisites, side effects, or confirm what happens to the savings goal balance, though the output schema means return values need not be described.

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 description coverage is 67%, with accountUid, savingsGoalUid, and the nested currency/minorUnits fields documented in the schema. The description adds no parameter meaning, but the schema carries most of the burden, making this minimally adequate.

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

Purpose2/5

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

The description 'Withdraw money from a savings goal' is a tautology that restates the tool name and title. It states a verb and resource but offers no differentiation from siblings like savings_goal_deposit or insight into scope.

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 guidance on when to use this tool versus savings_goal_deposit, nor any mention of prerequisites such as sufficient funds or goal state. The description provides no usage context.

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