Skip to main content
Glama

Arkanum Data: SEC insider trades

5%+ stakes

big_stakes
Read-only

Stakes of 5% or more in a company, from 13D and 13G filings by the funds and companies Arkanum tracks, newest first. Hobby and Pro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "big_stakes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
tickerNo
filed_fromNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 real behavioral context beyond that: the data originates from 13D/13G filings, coverage is limited to 'funds and companies Arkanum tracks', results are sorted newest first, and access requires the Hobby or Pro plan.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the resource, source, ordering and plan tier, and no filler. Nothing in it could be dropped without losing information.

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?

For a simple read-only list tool with no output schema, the description covers what the data is and where it comes from, but leaves the undocumented ticker and limit parameters ambiguous and gives no sense of result volume or pagination. Adequate, with clear gaps.

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

Parameters2/5

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

Schema description coverage is only 33%: only filed_from carries a format note (YYYY-MM-DD). Neither limit nor ticker is documented in the schema, and the description says nothing about them, so the agent gets no guidance on ticker format (symbol vs. name) or the default/ceiling of limit.

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 resource (stakes of 5% or more in a company) and the exact source (13D and 13G filings), plus the ordering (newest first). That is enough to distinguish it from insider-trade siblings, though it never explicitly contrasts itself with the closest-looking alternative, fund_holdings.

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 named alternative. The only contextual note is 'Hobby and Pro', which is a plan gate rather than a selection rule, so the agent must infer the use case from the resource description alone.

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