Skip to main content
Glama
Sign In
Investec OpenAPI MCP Server

Investec OpenAPI MCP Server

by jonelgithub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

investec_card_get_env_vars

Get environment variables (secrets and constants) configured for a card's code by providing the card key.

Instructions

Retrieve environment variables (secrets/constants) configured for a card's code.

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_env_vars"
  }
}

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?

No annotations are provided, so the description carries full burden. It only says 'Retrieve', implying no side effects, but does not confirm idempotency, access requirements, or error cases. For a read-only tool, minimal transparency is acceptable but could be improved by stating it is safe and does not modify state.

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, efficient sentence that front-loads the purpose. No redundant or vague wording. It earns its place without unnecessary detail.

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?

Despite the tool having one parameter and no nested objects, there is no output schema, and the description does not explain the return format (e.g., key-value pairs). For a retrieval tool, this omission reduces completeness. More detail on what the retrieved data looks like would be helpful.

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?

There is one parameter (cardKey) with 100% schema description coverage. The description does not add any additional meaning beyond what the schema already provides for the parameter. Baseline 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 action (Retrieve) and resource (environment variables for a card's code). It specifies the domain (card's code) and differentiates from siblings like investec_card_update_env_vars, which is the update counterpart.

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 when to use this tool (when needing to read environment variables), but does not explicitly state when not to use it or mention alternatives. No prerequisites or context for selection among siblings is provided.

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