Investec OpenAPI MCP Server

investec_pb_get_document

Retrieve a bank statement or tax certificate document with metadata and download link by providing account, document type, and date.

Instructions

Retrieve a specific document or statement file (returns metadata and document link).

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>",
      "documentType": "<documentType>",
      "documentDate": "<documentDate>"
    },
    "name": "investec_pb_get_document"
  }
}

Input Schema

Name	Required	Description
`accountId`	Yes	The unique identifier of the bank account
`documentDate`	Yes	Date of document (format: YYYY-MM-DD)
`documentType`	Yes	Type of document, typically 'Statement' or 'TaxCertificate'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 25, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The description mentions the return type (metadata and document link) but does not disclose whether the operation is read-only, any authentication requirements, rate limits, or side effects. With no annotations, the burden is higher, and the description falls short.

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?

The description is a single sentence that front-loads the key action and object. It is concise with no unnecessary words.

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 tool with three required parameters, no output schema, and no annotations, the description is minimal. It does not explain what metadata is included, how to use the returned link, or any error conditions, leaving significant gaps.

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?

The input schema has 100% coverage with descriptions for all three parameters. The description adds no additional meaning beyond the schema, so a 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 the tool retrieves a specific document or statement file, using the verb 'Retrieve' and specifying the resource. This distinguishes it from the sibling tool 'investec_pb_get_documents' which likely retrieves multiple documents.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'investec_pb_get_documents'). There is no mention of prerequisites, contextual cues, or when not to use it.

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

Deploy Server