Investec OpenAPI MCP Server

investec_pb_transfer_multiple

Initiate multiple transfers between your own Investec accounts. Specify source account, target accounts, amounts, and references for each transfer.

Instructions

Initiate transfers between own accounts (inter-account transfers).

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": {
      "accountId": "<accountId>",
      "paymentList": "<paymentList>"
    },
    "name": "investec_pb_transfer_multiple"
  }
}

Input Schema

Name	Required	Description	Default
`accountId`	Yes	The source bank account ID to transfer from
`paymentList`	Yes	Array of transfer instructions

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 25, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It mentions 'transfers between own accounts' but omits details such as authorization requirements, reversibility, fees, or potential side effects. This is a significant gap for a mutation operation.

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

Conciseness5/5

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

A single, focused sentence with no extraneous information. Every word is necessary, and the phrasing is straightforward.

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?

The description covers the basic purpose but lacks details about return values, error handling, batch behavior, or any prerequisites. For a multi-transfer operation, more context on success/failure handling would improve completeness.

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 100%, so the input schema already documents all parameters clearly. The description adds context ('own accounts') but does not enhance parameter meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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 'Initiate transfers between own accounts (inter-account transfers).' It specifies the verb 'Initiate transfers' and the resource 'own accounts', distinguishing it from sibling tools like investec_pb_pay_multiple, which likely handles external payments.

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 usage for inter-account transfers but provides no explicit guidance on when to use this tool versus alternatives (e.g., pay_multiple). No contrast or context is given, leaving the agent to infer based on sibling tool names.

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

Deploy Server