Skip to main content
Glama

AIsa Equities

by one.aisa
OverviewDiscussionsAdmin

Get Insider Trades

get_financial_insider_trades
Read-onlyIdempotent

Get insider trades like buys and sells for a ticker by a company insider.

Published reference price: $0.02 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
nameNoFilter by insider name (e.g., 'Jen Hsun Huang'). Use the /insider-trades/names endpoint to get available names for a ticker.
limitNoThe maximum number of transactions to return (default: 10). This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`. Provider reference (supplier schema): `{"default":10,"type":"integer"}`.
cursorNoOpaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.
tickerNoThe ticker symbol of the company.
form_typeNoFilter by SEC form type: 4 for trades, 5 for annual statements (or their amendments 4/A, 5/A).
filing_dateNoFilter by exact filing date in YYYY-MM-DD format. Provider reference (supplier schema): `{"format":"date","type":"string"}`.
filing_date_gtNoFilter by filing date greater than this date (YYYY-MM-DD). Provider reference (supplier schema): `{"format":"date","type":"string"}`.
filing_date_ltNoFilter by filing date less than this date (YYYY-MM-DD). Provider reference (supplier schema): `{"format":"date","type":"string"}`.
filing_date_gteNoFilter by filing date greater than or equal to this date (YYYY-MM-DD). Provider reference (supplier schema): `{"format":"date","type":"string"}`.
filing_date_lteNoFilter by filing date less than or equal to this date (YYYY-MM-DD). Provider reference (supplier schema): `{"format":"date","type":"string"}`.
transaction_typeNoFilter by transaction type (e.g., 'Open market sale', 'Gift'). Use the /insider-trades/transaction-types endpoint to get available types.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.",
+  "type": "string"
+}
    • addedInput schema / properties / filing_date
      Added value: +{
+  "description": "Filter by exact filing date in YYYY-MM-DD format.\n\nProvider reference (supplier schema): `{\"format\":\"date\",\"type\":\"string\"}`.",
+  "type": "string"
+}
    • addedInput schema / properties / filing_date_gt
      Added value: +{
+  "description": "Filter by filing date greater than this date (YYYY-MM-DD).\n\nProvider reference (supplier schema): `{\"format\":\"date\",\"type\":\"string\"}`.",
+  "type": "string"
+}
    • addedInput schema / properties / filing_date_gte
      Added value: +{
+  "description": "Filter by filing date greater than or equal to this date (YYYY-MM-DD).\n\nProvider reference (supplier schema): `{\"format\":\"date\",\"type\":\"string\"}`.",
+  "type": "string"
+}
    • addedInput schema / properties / filing_date_lt
      Added value: +{
+  "description": "Filter by filing date less than this date (YYYY-MM-DD).\n\nProvider reference (supplier schema): `{\"format\":\"date\",\"type\":\"string\"}`.",
+  "type": "string"
+}
    • addedInput schema / properties / filing_date_lte
      Added value: +{
+  "description": "Filter by filing date less than or equal to this date (YYYY-MM-DD).\n\nProvider reference (supplier schema): `{\"format\":\"date\",\"type\":\"string\"}`.",
+  "type": "string"
+}
    • addedInput schema / properties / form_type
      Added value: +{
+  "description": "Filter by SEC form type: 4 for trades, 5 for annual statements (or their amendments 4/A, 5/A).",
+  "enum": [
+    "4",
+    "4/A",
+    "5",
+    "5/A"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / limit / description
      Added value: +"The maximum number of transactions to return (default: 10). This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`.\n\nProvider reference (supplier schema): `{\"default\":10,\"type\":\"integer\"}`."
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Filter by insider name (e.g., 'Jen Hsun Huang'). Use the /insider-trades/names endpoint to get available names for a ticker.",
+  "type": "string"
+}
    • addedInput schema / properties / ticker / description
      Added value: +"The ticker symbol of the company."
    • addedInput schema / properties / transaction_type
      Added value: +{
+  "description": "Filter by transaction type (e.g., 'Open market sale', 'Gift'). Use the /insider-trades/transaction-types endpoint to get available types.",
+  "type": "string"
+}
  2. Changed12 schema fields changed
    • removedInput schema / properties / filing_date
      Removed value: -{
-  "description": "Filter by exact filing date in YYYY-MM-DD format.",
-  "format": "date",
-  "type": "string"
-}
    • removedInput schema / properties / filing_date_gt
      Removed value: -{
-  "description": "Filter by filing date greater than this date (YYYY-MM-DD).",
-  "format": "date",
-  "type": "string"
-}
    • removedInput schema / properties / filing_date_gte
      Removed value: -{
-  "description": "Filter by filing date greater than or equal to this date (YYYY-MM-DD).",
-  "format": "date",
-  "type": "string"
-}
    • removedInput schema / properties / filing_date_lt
      Removed value: -{
-  "description": "Filter by filing date less than this date (YYYY-MM-DD).",
-  "format": "date",
-  "type": "string"
-}
    • removedInput schema / properties / filing_date_lte
      Removed value: -{
-  "description": "Filter by filing date less than or equal to this date (YYYY-MM-DD).",
-  "format": "date",
-  "type": "string"
-}
    • removedInput schema / properties / limit / default
      Removed value: -10
    • removedInput schema / properties / limit / description
      Removed value: -"The maximum number of transactions to return (default: 10)."
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"string"
    • removedInput schema / properties / name
      Removed value: -{
-  "description": "Filter by insider name (e.g., 'Jen Hsun Huang'). Use the /insider-trades/names endpoint to get available names for a ticker.",
-  "type": "string"
-}
    • removedInput schema / properties / ticker / description
      Removed value: -"The ticker symbol of the company."
    • removedInput schema / properties / transaction_type
      Removed value: -{
-  "description": "Filter by transaction type (e.g., 'Open market sale', 'Gift'). Use the /insider-trades/transaction-types endpoint to get available types.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "ticker"
-]New value: +[]
  3. Changed12 schema fields changed
    • addedInput schema / properties / filing_date
      Added value: +{
+  "description": "Filter by exact filing date in YYYY-MM-DD format.",
+  "format": "date",
+  "type": "string"
+}
    • addedInput schema / properties / filing_date_gt
      Added value: +{
+  "description": "Filter by filing date greater than this date (YYYY-MM-DD).",
+  "format": "date",
+  "type": "string"
+}
    • addedInput schema / properties / filing_date_gte
      Added value: +{
+  "description": "Filter by filing date greater than or equal to this date (YYYY-MM-DD).",
+  "format": "date",
+  "type": "string"
+}
    • addedInput schema / properties / filing_date_lt
      Added value: +{
+  "description": "Filter by filing date less than this date (YYYY-MM-DD).",
+  "format": "date",
+  "type": "string"
+}
    • addedInput schema / properties / filing_date_lte
      Added value: +{
+  "description": "Filter by filing date less than or equal to this date (YYYY-MM-DD).",
+  "format": "date",
+  "type": "string"
+}
    • addedInput schema / properties / limit / default
      Added value: +10
    • addedInput schema / properties / limit / description
      Added value: +"The maximum number of transactions to return (default: 10)."
    • changedInput schema / properties / limit / type
      Previous value: -"string"New value: +"integer"
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Filter by insider name (e.g., 'Jen Hsun Huang'). Use the /insider-trades/names endpoint to get available names for a ticker.",
+  "type": "string"
+}
    • addedInput schema / properties / ticker / description
      Added value: +"The ticker symbol of the company."
    • addedInput schema / properties / transaction_type
      Added value: +{
+  "description": "Filter by transaction type (e.g., 'Open market sale', 'Gift'). Use the /insider-trades/transaction-types endpoint to get available types.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "ticker"
+]
  4. Changed12 schema fields changed
    • removedInput schema / properties / filing_date
      Removed value: -{
-  "description": "Filter by exact filing date in YYYY-MM-DD format.",
-  "format": "date",
-  "type": "string"
-}
    • removedInput schema / properties / filing_date_gt
      Removed value: -{
-  "description": "Filter by filing date greater than this date (YYYY-MM-DD).",
-  "format": "date",
-  "type": "string"
-}
    • removedInput schema / properties / filing_date_gte
      Removed value: -{
-  "description": "Filter by filing date greater than or equal to this date (YYYY-MM-DD).",
-  "format": "date",
-  "type": "string"
-}
    • removedInput schema / properties / filing_date_lt
      Removed value: -{
-  "description": "Filter by filing date less than this date (YYYY-MM-DD).",
-  "format": "date",
-  "type": "string"
-}
    • removedInput schema / properties / filing_date_lte
      Removed value: -{
-  "description": "Filter by filing date less than or equal to this date (YYYY-MM-DD).",
-  "format": "date",
-  "type": "string"
-}
    • removedInput schema / properties / limit / default
      Removed value: -10
    • removedInput schema / properties / limit / description
      Removed value: -"The maximum number of transactions to return (default: 10)."
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"string"
    • removedInput schema / properties / name
      Removed value: -{
-  "description": "Filter by insider name (e.g., 'Jen Hsun Huang'). Use the /insider-trades/names endpoint to get available names for a ticker.",
-  "type": "string"
-}
    • removedInput schema / properties / ticker / description
      Removed value: -"The ticker symbol of the company."
    • removedInput schema / properties / transaction_type
      Removed value: -{
-  "description": "Filter by transaction type (e.g., 'Open market sale', 'Gift'). Use the /insider-trades/transaction-types endpoint to get available types.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "ticker"
-]New value: +[]
  5. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful pricing context ($0.02 per successful request), but does not disclose rate limits, authentication needs, or edge cases like what happens when no ticker is provided.

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 core description is a single efficient sentence, front-loading the purpose. The pricing block is boilerplate but standard, and does not detract significantly from conciseness.

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

Completeness3/5

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

With a rich output schema and detailed annotations, the description needs only to orient the agent. However, it implies that a ticker is required ('for a ticker') when the schema marks it optional, and it omits any mention of the many available filters (name, form type, dates), which could lead to underutilization or confusion.

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 description coverage is 100%, so the schema fully documents all 11 parameters. The description adds no parameter-level meaning beyond what the schema already provides, making the baseline of 3 appropriate.

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 states a specific verb ('Get') and resource ('insider trades') and clarifies the scope ('for a ticker by a company insider'). It distinguishes from most siblings, though it doesn't explicitly differentiate from broader filings tools that might also contain insider information. Overall clear and direct.

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?

No guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states what the tool does, leaving the agent to infer context from the schema and tool name.

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

All AIsa Equities toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources