Skip to main content
Glama

Cabrini Market Data

by ai.cabrini

get_bars

Resampled intraday bars at custom timeframes (3, 6, 9, 12, 15, 30, 60, 240 min) for one ticker. Every bar carries absolute open/high/low/close plus fractional change from the daily open, whatever the interval, and volume and transactions. $0.015 USDC per day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoMulti-day end date
dateNoTrading date YYYY-MM-DD
startNoMulti-day start date
tickerYesStock ticker (e.g. AAPL)
adjustedNoApply split adjustment (default false)
intervalYesBar interval in minutes: 3, 6, 9, 12, 15, 30, 60, or 240

TDQS

A4.1/5.0
Behavior4/5

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

Describes output fields (OHLC, fractional change, volume, transactions) and cost ($0.015 per day). No annotations exist, so description carries full burden. Missing error conditions or auth requirements, but covers key behavioral traits.

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?

Two sentences, front-loaded with core purpose and data details. No redundant information, efficient and clear.

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

Completeness5/5

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

No output schema, but description fully explains return values (OHLC, fractional change, volume, transactions) and includes pricing. With no annotations, description provides sufficient context for agent to understand behavior.

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?

Schema coverage is 100%, baseline 3. Description mentions intervals and confirms resampling, but the schema already details the interval parameter. Adds minimal extra meaning beyond the schema.

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

Purpose5/5

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

Clearly states it fetches resampled intraday bars for one ticker at custom timeframes, listing allowed intervals. Distinguishes from siblings like query_minute_bars and query_daily by specifying the resampling nature and output fields.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage for intraday bar data analysis, but no explicit when-to-use or when-not-to-use compared to alternative tools. Lacks guidance on scenarios like when raw minute bars or daily bars are more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cabrini Market Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have distinct purposes, but there is some overlap among bar-related tools (get_bars, query_minute_bars, query_range, query_daily). Descriptions are detailed enough to differentiate, but an agent might need to carefully choose the right bar tool.

Naming Consistency4/5

Naming follows a consistent verb_noun pattern (get_*, query_*, scan_*). The only minor deviation is list_tickers instead of get_tickers, but it's still predictable.

Tool Count5/5

15 tools is well-scoped for a market data API covering prices, fundamentals, filings, insiders, and screening. Each tool serves a clear purpose without being excessive.

Completeness5/5

The tool set covers a comprehensive range of market data needs: intraday/daily bars, fundamentals, SEC filings, insider transactions, company profiles, and screening. Notable missing features like options data are beyond the stated scope.

Resources