Skip to main content
Glama
Sign In
blpapi-mcp

blpapi-mcp

by djsamseng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bdib

Get Bloomberg intraday bar data for a ticker on a specific date. Customize session and bar type for trade data.

Instructions

Get Bloomberg intraday bar 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": {
      "ticker": "<ticker>",
      "dt": "<dt>"
    },
    "name": "bdib"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes
dtYes
sessionNoallday
typNoTRADE
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?

With no annotations provided, the description bears the full burden. It fails to disclose whether the operation is read-only, any rate limits, or error behavior. The minimal description provides no behavioral context.

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

Conciseness3/5

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

The description is a single short sentence, which is concise but lacks essential details. It is not overly long, but conciseness here sacrifices completeness.

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 the complexity (5 parameters, no output schema, no annotations), the description is severely inadequate. It does not explain return value, parameter formats, or how to use the tool correctly.

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?

Schema description coverage is 0%, and the description does not explain any of the 5 parameters (ticker, dt, session, typ, kwargs). The agent has no clue what formats to use for 'dt' or 'session'.

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?

The description 'Get Bloomberg intraday bar data' clearly states the verb and resource, and distinguishes from siblings like bdh (historical data) and bdtick (tick data). However, it could be more specific (e.g., 'including OHLCV').

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 this tool versus alternatives like bdh or bdp. The description lacks any context about appropriate usage or prerequisites.

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