Skip to main content
Glama
Sign In
Investec OpenAPI MCP Server

Investec OpenAPI MCP Server

by jonelgithub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

investec_card_get_published_code

Retrieve the currently active JavaScript code running on a programmable Investec card.

Instructions

Retrieve the currently active/published JavaScript code running on the programmable card.

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": {
      "cardKey": "<cardKey>"
    },
    "name": "investec_card_get_published_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardKeyYesThe unique key identifying the card

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

Without annotations, the description carries full burden. It only states the retrieval action but does not disclose whether it is read-only, any required permissions, or error conditions. Minimal behavioral insight.

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?

Single sentence with 12 words, no redundancy. Front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple retrieval tool with one parameter and no output schema, the description is fairly complete. It hints at a published vs draft distinction, which adds context. Could mention return format or empty state, but not critical.

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 coverage is 100% with a single parameter 'cardKey' described as 'The unique key identifying the card'. The description adds no additional 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 action ('Retrieve') and specific resource ('currently active/published JavaScript code'), distinguishing it from siblings like investec_card_get_code (which may retrieve draft code) and investec_card_publish_code.

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 versus related tools (e.g., investec_card_get_code, investec_card_execute_code) or any prerequisites. The description lacks explicit when-to-use or when-not-to-use context.

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