blpapi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bdpD | Get Bloomberg reference data |
| bdsC | Get Bloomberg block data |
| bdhC | Get Bloomberg historical data |
| bdibC | Get Bloomberg intraday bar data |
| bdtickC | Get Bloomberg tick data |
| earningC | Get Bloomberg earning exposure by Geo or Products |
| dividendD | Get Bloomberg divident / split history |
| beqsD | Get Bloomberg equity screening |
| turnoverC | Calculate the adjusted turnover (in millions) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct Bloomberg data type (historical, intraday, reference, block data, ticks, screening, dividends, earnings, turnover), with clear descriptions preventing confusion.
Tool names mix Bloomberg-specific acronyms (bdh, bdib, bdp, bds, bdtick, beqs) with full words (dividend, earning, turnover), lacking a uniform pattern. Acronyms vary in length and structure.
Nine tools cover the core Bloomberg data retrieval needs without overloading; the count is appropriate for a financial data server.
Covers major data types (historical, intraday, reference, screening) but misses real-time data and some corporate actions (e.g., stock splits, M&A). Minor gaps exist but core workflows are functional.