Skip to main content
Glama

Arkanum Data: SEC insider trades

Find an insider

search_insiders
Read-only

Find officers and directors by name. Returns each one's SEC ID (CIK) and companies, for get_insider.

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": {
      "q": "<q>"
    },
    "name": "search_insiders"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesPart of a name, e.g. Jensen Huang
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 the return shape (CIK plus companies), which is useful, but says nothing about the 20-result default, the 50 cap, or what happens on ambiguous/no matches.

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?

Two short sentences, front-loaded with the verb and resource, then the return value and the follow-up target. No 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?

For a simple two-parameter read-only lookup with no output schema, the description covers trigger, return contents, and next step. Only the paging/limit behavior is left open, which is a minor gap at this complexity.

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 50%: 'q' is documented in the schema and the description reinforces that it is a name fragment, but 'limit' is undocumented in both places. Baseline 3 is appropriate since the required parameter is fully covered and the description adds no syntax beyond the schema.

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 verb and resource ('Find officers and directors by name') plus what comes back (SEC ID/CIK and companies), which distinguishes it from trade-history siblings. It does not explicitly compare itself to siblings like search_insider_history, but the lookup-vs-data framing is clear.

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?

'for get_insider' tells the agent this is a name-to-CIK resolution step that feeds a follow-up call, which is genuine when-to-use guidance. It stops short of exclusions (e.g., that it returns no trade data, so use search_insider_trades for that), leaving inference to the agent.

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