Skip to main content
Glama

Arkanum Data: SEC insider trades

Latest insider trades (today)

latest_insider_trades
Read-only

Today's insider-trade filings, refreshed hourly. Pass since (the updated value from your previous call) and an unchanged file returns no trades. 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": "latest_insider_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO time from a previous call's `updated`

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 safety is covered. The description adds real behavior beyond that: hourly refresh cadence, delta semantics via `since` where an unchanged result returns empty, and plan-tier availability ("Hobby and Pro"). It does not state rate limits or the shape of a returned trade, keeping it below a 5.

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?

Three short sentences, front-loaded with what the tool returns and when, then the polling mechanic. Every clause carries operational meaning; "Hobby and Pro" is terse but informative rather than filler.

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?

This is a simple single-optional-parameter read tool, and the description covers cadence, incremental polling, and plan availability. Because there is no output schema, the reference to an `updated` field in the response is left undefined — the agent must discover that field empirically — which is the only notable gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining the delta contract — pass the `updated` value from the prior call and an unchanged file returns no trades — which tells the agent why the parameter exists, not just its type. It does not clarify format edge cases (timezone, whether `since` is inclusive).

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?

Names a specific resource and scope: "Today's insider-trade filings," which is meaningfully narrower than the sibling search_insider_trades or search_insider_history. It does not explicitly name a sibling to differentiate itself, so an agent must infer that this is the today-only feed, but the resource and time window are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context for polling: pass `since` from a previous call, and an unchanged file yields no trades — exactly the pattern an agent needs for incremental refresh. It stops short of explicitly excluding alternatives (e.g., "for history or non-today ranges use search_insider_history"), so it lands at 4 rather than 5.

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