Investec OpenAPI MCP Server

investec_pb_get_documents

List available PDF documents such as statements and tax certificates for an account, with optional from and to date filters.

Instructions

List available PDF documents (such as statements and tax certificates) for an account. Supports optional fromDate and toDate filters.

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>"
    },
    "name": "investec_pb_get_documents"
  }
}

Input Schema

Name	Required	Description
`toDate`	No	Filter documents to this date (format: YYYY-MM-DD)
`fromDate`	No	Filter documents from this date (format: YYYY-MM-DD)
`accountId`	Yes	The unique identifier of the bank account

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description must bear the full behavioral disclosure. It states it lists PDF documents but does not describe the return format (e.g., list of document metadata) or whether pagination is used. For a simple list tool, this is adequate but lacks depth.

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?

Two sentences front-loaded with the action and resource, followed by optional filters. No redundant information. Slightly hampered by lack of details on output, but still concise.

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 functionality but does not explain what the list returns (likely an array of document references) or if there are limits/pagination. Given no output schema, more context on the response would be helpful but is not strictly required.

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 baseline is 3. The description adds context about document types ('such as statements and tax certificates') and reinforces the optional filters, but does not add significant new meaning beyond the schema.

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 lists PDF documents for an account, specifying the resource (PDF documents), verb (list), and scope (for an account). It distinguishes itself from the sibling investec_pb_get_document (singular) which likely retrieves a single document.

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 indicates optional date filters but does not provide explicit guidance on when to use this tool versus alternatives. The sibling name difference (plural vs singular) implies this is for listing, but no exclusions or prerequisites are mentioned.

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

Deploy Server