Skip to main content
Glama

Trading Signals Toolkit

SEC Insider Buys (ticker)

insider_buys
Read-only

SEC Form 4 open-market insider purchases (code P) for one ticker: insider, role, shares, price, value, dates, per-insider totals and a cluster flag. From SEC EDGAR. Read-only, never places orders. Informational only, not investment advice.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLookback in days (1-90, default 30)
tickerYesUS equity ticker, e.g. AAPL or BRK-B

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint, so 'Read-only, never places orders' largely restates structured data. The description does add the data provenance ('From SEC EDGAR'), which is useful context beyond annotations, but it omits freshness/latency, coverage limits, and whether the cluster flag has a defined threshold.

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?

A single dense sentence delivers source, scope, filter criterion, and return fields up front, followed by a short safety disclaimer. It is efficient, though the comma-separated field list is slightly heavy and the disclaimer repeats annotation content.

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 only two required-well-documented parameters and no output schema, the description compensates by enumerating the returned fields (insider, role, shares, price, value, dates, per-insider totals, cluster flag). That is enough to call the tool confidently; only data freshness and the cluster-flag definition are missing.

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 schema already documents the ticker format and the days range with its default of 30. The description adds no meaning beyond that, so the baseline of 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 source and record type ('SEC Form 4 open-market insider purchases (code P)') plus the scope ('for one ticker') and even lists the returned fields. It is unambiguous what the tool does, but it never names or distinguishes itself from the sibling insider_clusters, which appears to cover adjacent territory.

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 guidance, no prerequisites, and no routing to alternatives such as insider_clusters for cluster-focused analysis. 'Informational only, not investment advice' is a disclaimer, not usage guidance.

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