Skip to main content
Glama

BRAINIAC Company Intelligence

Get company filings

company-intelligence_filings

Retrieve recent company filings and significant changes from SEC EDGAR using CIK or ticker. Price $0.05 USDC. POST /api/v1/company-intelligence/filings. Unpaid calls return 402 and do not run.

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": {
      "identifier": "<identifier>"
    },
    "name": "company-intelligence_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses cost ($0.05 USDC), the endpoint, and the unpaid-call failure mode (402, no execution). It does not say what "recent" means, how results are paginated or capped, or how errors other than 402 behave.

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?

Four short sentences, each carrying distinct information, with the core purpose front-loaded ahead of pricing and transport details. The endpoint path is arguably redundant for an agent but not harmful.

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 no output schema and no annotations, the description should say more about what comes back (filing types, form fields, ordering) and about the unexplained `limit` parameter. Cost and failure-mode disclosure is good, but the return shape and result semantics are missing.

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 0%, so the description must compensate. It clarifies that the required identifier accepts either a CIK or a ticker, which the schema does not say, but the `limit` parameter is left completely unexplained despite its 1-100 bounds.

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?

States a specific verb and resource (retrieve company filings and significant changes) plus the source (SEC EDGAR) and accepted identifier types (CIK or ticker). That makes it distinguishable from siblings like financials or ownership, but it never explicitly contrasts itself with them.

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?

There is no when-to-use or when-not-to-use guidance and no reference to the sibling tools (financials, ownership, profile, search) that an agent would otherwise have to choose between. Usage is only implied by the resource name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources