Skip to main content
Glama

Arkanum Data: SEC insider trades

One insider

get_insider
Read-only

One insider's companies and roles, shares held after their latest filing at each, and their recent open-market trades. Hobby and Pro also get their trading pattern (routine or opportunistic).

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": {
      "cik": "<cik>"
    },
    "name": "get_insider"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesThe insider's SEC ID, from search_insiders or a trade

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 one genuinely useful behavioral detail beyond them — that the trading pattern field is only returned for Hobby and Pro plans — but says nothing about authorization, plan limits on other data, or error behavior.

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?

Two tight sentences that front-load the returned data and end with the plan-gated extra field. Minor friction from the unexplained 'Hobby and Pro' plan names, but no wasted wording.

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?

With one fully documented parameter, no output schema, and read-only annotations, the description covers the main gap an agent would have: what data comes back and the one plan-dependent field. Only the flow from search_insiders to this call is left implicit.

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 100% and the single 'cik' parameter is already documented as 'The insider's SEC ID, from search_insiders or a trade', which supplies both meaning and provenance. The description adds no additional detail about the identifier, so the 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 resource ('One insider's companies and roles, shares held... recent open-market trades') and implicitly contrasts with the plural search_insiders by emphasizing a single insider. It is clear what the tool returns, though it never explicitly frames itself as the single-insider lookup versus the search siblings.

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 by 'One insider's' — an agent can infer this is the detail lookup after finding a CIK, but the description never states when to prefer it over search_insiders, latest_insider_trades, or search_insider_history. No exclusions or preconditions are given.

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