Skip to main content
Glama
Sign In
blpapi-mcp

blpapi-mcp

by djsamseng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bdp

Retrieve Bloomberg reference data for specified tickers and fields. Obtain static financial information like company details or security characteristics.

Instructions

Get Bloomberg reference data

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": {
      "tickers": "<tickers>",
      "flds": "<flds>",
      "kwargs": "<kwargs>"
    },
    "name": "bdp"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYes
fldsYes
kwargsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are present, and the description does not disclose any behavioral traits (e.g., read-only, idempotent, rate limits). The agent is left without critical information about side effects or constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (3 words) but misses essential information. Conciseness should not come at the cost of completeness; here it is under-specified.

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

Completeness1/5

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

With 3 required parameters, nested objects, no output schema, and no sibling differentiation, the description is grossly insufficient for correct tool invocation.

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

Parameters1/5

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

The schema has 0% description coverage for parameters, and the tool description does not explain tickers, flds, or kwargs. An agent cannot infer expected formats, allowed values, or semantics from the given text.

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

Purpose2/5

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

The description 'Get Bloomberg reference data' is vague; it does not specify what 'reference data' includes or how it differs from sibling tools like bdh or bds. The verb 'Get' is clear but the resource is ambiguous.

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 bdp versus alternatives such as bds or bdh. No context about prerequisites, typical use cases, or exclusions 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