Skip to main content
Glama

equibles

by io.github.daniel3303

Insider Transactions (Forms 4/5)

GetInsiderTransactions
Read-only

Get recent insider trading transactions for a stock from SEC Forms 4 and 5, newest first. Form 3 supplies initial ownership rather than a transaction. The Type column carries the SEC transaction code meaning: 'Buy'/'Sell' are open-market purchases/sales only, while Award, Conversion, Exercise, Tax Payment, Expiration, Gift, Inheritance, Discretionary and Other are compensation or derivative mechanics — not conviction trades. The 10b5-1 column marks trades made under a pre-arranged Rule 10b5-1 plan ('-' = filing predates the 2023 checkbox). Per-row Shares/Price/Value are as filed; Owned After is the post-transaction balance restated onto today's split basis, tracked per security kind and ownership form. Supports optional date-range, transaction-type and insider-name filters to reach history beyond the newest rows. Use this to understand insider buying/selling activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoNumber of matching transactions to skip before returning rows (default: 0)
tickerYesCompany ticker symbol (e.g., AAPL, MSFT)
toDateNoOnly include transactions on or before this date, format yyyy-MM-dd (optional)
fromDateNoOnly include transactions on or after this date, format yyyy-MM-dd (optional)
maxResultsNoMaximum number of transactions to return (default: 50, max: 500; values outside 1-500 are clamped)
insiderNameNoOnly include transactions by insiders whose SEC-filed name contains every word of this value, case-insensitive (e.g. 'Huang') (optional)
transactionTypeNoOnly include one transaction type: Buy, Sell, Award, Conversion, Exercise, TaxPayment, Expiration, Gift, Inheritance, Discretionary or Other (optional)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of matching transactions to skip before returning rows (default: 0)",
+  "type": "integer"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's value lies in interpretation, and it delivers: it explains that Buy/Sell are open-market only while other types are compensation/derivative mechanics, decodes the 10b5-1 column, and clarifies that Owned After is split-restated. This prevents common misreadings of the data.

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?

The description is long but information-dense, with the core action front-loaded in the first sentence. Every sentence earns its place by adding scope, column semantics, or a caveat; minor formatting improvements could make it punchier, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining return semantics, and it covers ordering, form source, column meanings, split adjustment, and filter reach. Combined with fully documented schema parameters, an agent has enough to invoke the tool correctly and interpret the results.

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 description coverage is 100%, so baseline is 3. The description adds practical meaning by explaining what transactionType values represent ('Buy'/'Sell' are open-market only; others are mechanics) and why date-range, transaction-type, and insider-name filters exist, going beyond bare schema format documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Get recent insider trading transactions for a stock from SEC Forms 4 and 5, newest first' — and distinguishes Form 3 as initial ownership rather than a transaction. This makes the tool's scope immediately recognizable and separable from sibling tools like GetInsiderOwnership and GetInsiderSentimentScores.

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?

Gives clear context: the tool is for understanding insider buying/selling activity and can reach history beyond newest rows via filters. It also clarifies what Form 3 is not, but it does not explicitly name sibling alternatives or state when to prefer GetInsiderOwnership versus this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All equibles toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions that cross-reference related alternatives. A few near-duplicate names could cause misselection, notably SearchDocument versus SearchDocuments and GetCftcPositioning versus GetLatestCftcPositioning.

Naming Consistency5/5

Tool names consistently follow a VerbNoun camelCase pattern: Get for retrievals, Search for discovery, List/Read for document access, and Add/Close/Remove/Update/Watch/Create/Delete for portfolio mutations. Despite the large count, there is no mixing of naming conventions or unpredictable verb styles.

Tool Count1/5

108 tools is an extreme surface area, far beyond the 3-15 well-scoped range and well past the 25+ threshold. Even for a broad financial data platform, this creates a heavy selection burden and substantial context overhead for agents.

Completeness4/5

The server covers an unusually wide domain: prices, fundamentals, SEC filings, options, insider activity, 13F holdings, short interest, macro data, funds, IPOs, and full portfolio lifecycle management. Notable gaps remain, such as a basic company profile/ticker-resolution tool, dividend history, and analyst estimates, so it is not a perfect 5.

Resources