Skip to main content
Glama
Sign In
Investec OpenAPI MCP Server

Investec OpenAPI MCP Server

by jonelgithub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

investec_ifi_get_client_dashboard

Retrieve client dashboard summary including holdings and client details by searching with a keyword such as client name or account number.

Instructions

Query and view the client dashboard summary by keyword (client details, holdings).

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": {
      "searchKeyword": "<searchKeyword>"
    },
    "name": "investec_ifi_get_client_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchKeywordYesSearch term for client name, account, etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided; description only says 'Query and view' implying read-only, but does not disclose permissions, rate limits, or any side effects. Full burden is on description, which is insufficient.

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?

Description is a single sentence with no redundancy. Action is front-loaded. Could be slightly more structured, but overall concise and efficient.

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?

No output schema exists, but description does not explain return format or fields beyond 'client details, holdings'. Lacks usage examples or context about what 'dashboard summary' includes. Incomplete for a query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter 'searchKeyword' has schema description 'Search term for client name, account, etc.' which aligns with tool description. Schema coverage is 100%, and description adds context by specifying acceptable values (client name, account), exceeding baseline.

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?

Description clearly states the action ('Query and view'), resource ('client dashboard summary'), and method ('by keyword'), with parenthetical indicating contents (client details, holdings). It distinguishes from sibling tools which focus on specific sub-areas like cards, CIB, or PB.

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 on when to use this tool vs alternatives (e.g., investec_ifi_list_accounts). Does not mention prerequisites, exclusions, or context for use.

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