Skip to main content
Glama
Sign In
bca-mcp

bca-mcp

by blockchainacademics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

track_sec_filings

Track SEC filings of publicly traded crypto companies using a ticker symbol. Retrieve regulatory documents for firms like MSTR, COIN, or HOOD.

Instructions

SEC filings for listed crypto companies. Starter tier.

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>"
    },
    "name": "track_sec_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYese.g. MSTR, COIN, HOOD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.6/5.0
Behavior1/5

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

No annotations are provided, and the description is extremely brief. It does not disclose whether the tool returns filing details, links, summaries, or any limitations. The agent has no information about mutation, rate limits, or data freshness.

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 only two sentences, front-loading the purpose. It is concise but could convey more useful information in the same space, such as output details.

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

Completeness2/5

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

With one required parameter, no output schema, and no annotations, the description is incomplete. It omits what the user will receive (e.g., filing dates, links) and any constraints of the Starter tier.

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?

There is only one parameter 'ticker' with a schema description giving examples. The tool description adds no extra meaning beyond the schema. With 100% schema coverage, baseline is 3.

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 'SEC filings for listed crypto companies' clearly states the domain and resource (SEC filings of crypto companies). The verb 'track' is implied by the tool name, and 'Starter tier' hints at subscription level. However, it does not differentiate from sibling track tools like track_pumpfun or track_bonkfun, which target different data types.

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. The sibling tools include many data retrieval tools, but the description provides no context for choosing this tool over, e.g., get_article or get_entity.

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