Skip to main content
Glama
Sign In
BlindPay MCP Server

BlindPay MCP Server

by blindpaylabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete Instances Customers Bank Accounts By Id

DeleteV1InstancesCustomersBankAccountsById
DestructiveIdempotent

Deletes a customer's bank account by ID within a specified instance to remove obsolete or incorrect payment details from BlindPay.

Instructions

Remove Bank Account

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": {
      "instance_id": "<instance_id>",
      "customer_id": "<customer_id>",
      "id": "<id>"
    },
    "name": "DeleteV1InstancesCustomersBankAccountsById"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
customer_idYesCustomer ID
instance_idYes
Idempotency-KeyNoOptional key to safely retry this request without performing the action twice. Retrying with the same key and an identical body replays the original response; reusing a key with a different body returns an error. Keys are kept for 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.3

TDQS

C2.3/5.0
Behavior2/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, and "Remove" is consistent with those. However, the description adds no behavioral context beyond restating deletion, such as irreversibility, side effects, or required permissions.

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

Conciseness2/5

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

Two words are concise but under-specify a destructive, multi-parameter operation. The brevity does not earn its place because essential scope and behavior are missing.

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?

For a destructive deletion tool with three required identifiers and 50% schema coverage, the description leaves out almost everything an agent needs: instance/customer scoping, effects of deletion, and retry semantics beyond the Idempotency-Key schema note. Annotations cover the safety hints, but the description itself is far from complete.

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?

The description mentions no parameters at all. With only 50% schema description coverage, the undocumented id and instance_id parameters must be inferred from their names and examples, and the description does not compensate for that gap.

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

Purpose3/5

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

The description gives a clear verb and resource with "Remove Bank Account", but it is extremely terse and omits the by-ID scope and instance/customer context embedded in the tool name. It does not differentiate this deletion from other bank-account operations such as GetV1InstancesCustomersBankAccountsById or the related create/list tools.

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 deletion versus related tools, nor any mention of prerequisites, consequences, or alternatives. An agent must infer usage entirely from the tool name and sibling list.

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