Skip to main content
Glama

Arkanum Data: SEC insider trades

Company risk flags

company_risk_flags
Read-only

Red flags and things worth knowing about one company, from its SEC filings: serious 8-K events (bankruptcy, delisting notices, restatements, auditor changes, cyber incidents, layoffs), repeated leadership changes, losses, cash burn, high debt, shrinking revenue, out-of-date financial statements and heavy insider selling. No stock prices. No flags means none of the checks found anything, not that the stock is safe. Hobby and Pro.

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": "company_risk_flags"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker, e.g. AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the data source is SEC filings, stock prices are explicitly out of scope, empty results carry a specific caveat, and access is limited to Hobby and Pro tiers. It does not state how far back the checks look or how fresh the underlying filings are.

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?

Purpose is front-loaded in the first clause, followed by the enumerated checks, then scope exclusions and the caveat. It is dense but every clause carries information; the long parenthetical list of 8-K event types is the only place it risks becoming a run-on.

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?

For a single-ticker read-only tool with no output schema, the description covers what is checked, what is explicitly excluded, how to interpret an empty response, and plan availability. An agent has enough to decide to call it and to interpret the result without further documentation.

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 a single required parameter at 100% schema coverage, and the schema already documents it as a stock ticker with an example. The description adds only indirect meaning — that the ticker must correspond to an SEC filer — without saying anything about format, case, or exchange-qualified symbols. Baseline 3 is appropriate when the schema does the work.

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 names a concrete resource (red flags for one company, derived from SEC filings) and enumerates the specific checks: 8-K events, leadership churn, losses, cash burn, debt, revenue trend, stale statements, insider selling. That is far more specific than a restatement of the name. It stops short of naming which sibling to use instead (e.g., get_company for raw fundamentals or market_warnings), so sibling differentiation is inferred rather than stated.

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?

Usage is implied by the content list rather than stated: an agent can infer this is a screening/due-diligence check on a single ticker. There is no explicit when-to-use versus when-not-to-use, nor any pointer to alternatives among the many sibling tools. The one strong guidance element is interpretive — that an empty result means no checks fired, not that the stock is safe.

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