Skip to main content
Glama

Cabrini Market Data

by ai.cabrini

get_filings

SEC filing index (10-K, 10-Q, 8-K, proxies) for a ticker. $0.01 USDC; add sections=[risk_factors, mdna] to extract full section text from the latest 10-K/10-Q for $0.05.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typesNoFilter to filing types, e.g. ["10-K", "8-K"]
tickerYesStock ticker (e.g. AAPL)
to_dateNoEnd date YYYY-MM-DD
sectionsNoExtract section text: risk_factors and/or mdna
accessionNoExtract sections from this specific filing accession number
from_dateNoStart date YYYY-MM-DD

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses pricing and section extraction behavior but does not mention data freshness, permissions, rate limits, or whether the operation is destructive. Adequate but incomplete.

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?

Two sentences, no wasted words. The second sentence is dense but still efficient. Could be slightly clearer by splitting pricing and extraction details.

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

Completeness3/5

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

No output schema, so description should explain return structure. It says 'filing index' but does not specify fields. Section extraction is explained well. Lacks details on pagination, response format, or error handling, which are needed for full completeness.

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

Parameters4/5

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

Schema coverage is 100%. Description adds meaning beyond schema: explains that sections extract text from latest 10-K/10-Q unless accession specified, and provides pricing context for sections parameter. This enhances understanding.

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?

The description clearly states the tool retrieves SEC filing index for a ticker, listing specific filing types (10-K, 10-Q, etc.) and optional section extraction. This distinguishes it from sibling tools like get_bars or get_pricing.

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?

The description mentions pricing but does not provide explicit when-to-use guidance or alternatives among siblings. Usage is implied for SEC filing retrieval, but no exclusions or comparisons.

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