Skip to main content
Glama
Sign In
blpapi-mcp

blpapi-mcp

by djsamseng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bdh

Retrieve historical Bloomberg data for specified tickers and fields over a customizable date range.

Instructions

Get Bloomberg historical 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>"
    },
    "name": "bdh"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYes
fldsYes
start_dateNo
end_dateNotoday
adjustNo
kwargsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are available, and the description lacks any behavioral disclosure such as read-only status, rate limits, or authentication requirements, leaving the agent uninformed about side effects or restrictions.

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?

The description is a single, concise sentence that front-loads the core purpose, but it lacks structure and additional detail that would improve usability without adding significant length.

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?

Given six parameters with no schema descriptions, no output schema, and complex sibling tools, the description is grossly incomplete; it fails to explain return format, data range semantics, or how 'adjust' and 'kwargs' affect the query.

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

Parameters2/5

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

The description adds no information about the six parameters; although parameter names like 'tickers' and 'flds' are somewhat self-explanatory, 'adjust' and 'kwargs' are ambiguous, and the 0% schema coverage means the description should compensate, which it does not.

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

Purpose3/5

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

The description states 'Get Bloomberg historical data', which is a clear verb+resource but does not differentiate from sibling tools like bdib (intraday bar data) or bdtick (tick data), all of which involve historical data retrieval.

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 usage guidelines are provided; the description does not indicate when to use this tool versus alternatives like bdp or bds, nor does it specify prerequisites or constraints.

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