Skip to main content
Glama
Sign In
Investec OpenAPI MCP Server

Investec OpenAPI MCP Server

by jonelgithub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

investec_cib_get_orders_shipments_report

Retrieve a corporate company's current orders and shipment status report by providing the company name.

Instructions

Get current orders and shipment status report for a corporate company.

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": {
      "companyName": "<companyName>"
    },
    "name": "investec_cib_get_orders_shipments_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyNameYesName of the corporate company

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided. Description only says 'Get' without stating read-only nature, side effects, rate limits, or required permissions. Minimal behavioral disclosure for a tool that likely involves no mutations.

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?

One-sentence description with 11 words, no wasted text. Concise and front-loaded.

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?

Given no output schema and no annotations, the description is adequate for a one-parameter tool but could be improved by mentioning the report format or that it returns order and shipment status data.

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 single parameter 'companyName' is fully described in the schema. The tool description does not add any information about the parameter beyond what the schema already provides, so scores at baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool retrieves an 'orders and shipment status report' for a corporate company, using a specific verb-resource pair. It distinguishes from sibling tools like investec_cib_get_account_transactions, though 'orders' could be more precise (e.g., purchase orders, sales orders).

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?

Description provides no guidance on when to use this tool versus alternatives (e.g., other investec_cib tools) or any prerequisites. There is no mention of context or exclusions.

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