Skip to main content
Glama

Arkanum Data: SEC insider trades

One company

get_company
Read-only

A company's identifiers, fundamentals from SEC filings (revenue, profit, margins, growth, debt, cash flow, dividends), insider buying and selling by month, its insiders, and its recent 8-K announcements in plain English. No stock prices.

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

Input Schema

NameRequiredDescriptionDefault
tickerYese.g. AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 useful behavioral context by listing the covered data domains and noting output is 'in plain English' (narrative, not raw JSON), but says nothing about result size, latency, or what happens for an unknown ticker – with annotations carrying the safety story, a 3 fits.

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?

One dense sentence that front-loads the resource and then enumerates contents, ending with a scoping exclusion. Every clause carries information, though the long parenthetical list of fundamentals is slightly crammed and could be structured more scannably.

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

Completeness4/5

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

For a single-parameter read-only tool with no output schema, the description adequately tells the agent what data domains come back, which is the main uncertainty. Only edge behavior (invalid ticker, empty results) is unaddressed, a minor gap given the tool's simplicity.

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 parameter, ticker, and schema description coverage is 100% with an example ('AAPL') already in the schema. The description adds no extra meaning about ticker format, exchange prefix, or case sensitivity, so the schema is doing all the work and baseline 3 applies.

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 specific verb+resource (a company) and enumerates its contents: identifiers, SEC fundamentals, insider activity, insiders, and 8-K announcements. The closing 'No stock prices' marks the boundary of what it returns, which helps separate it from price-oriented tools, though no sibling is named explicitly.

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 only implied: this is evidently the company overview entry point, and the 'No stock prices' clause tells the agent one case where it is the wrong choice. It never states when to prefer it over get_insider, get_filing, or insider-specific siblings, so the agent must infer routing from the content list.

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