Skip to main content
Glama

AINDEX

A stock's insiders and holders

insider_trades
Read-only

A US stock's insider trades (who, role, date, buy or sell, shares, price) with 3 and 12 month counts, its institutional ownership, and its largest holders with their latest change. From Nasdaq.

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_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

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=true and openWorldHint=true, so the safety profile is covered. The description adds real context beyond them: the data source (Nasdaq) and an explicit inventory of returned sections, but says nothing about rate limits, partial/empty results, or latency. Adequate against a low annotation bar, not rich.

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 front-loaded sentence that enumerates the payload efficiently with no filler. Parenthetical field lists keep it compact; slightly dense but nothing wasted.

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?

There is no output schema, so the description carries the burden of telling the agent what comes back, and it does so with a full section inventory. For a one-parameter read-only lookup, the remaining gaps (empty-result behavior, response nesting) are minor.

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 0%, but there is only one parameter and the pattern (^[A-Za-z.]{1,10}$) is self-evident. The description contributes meaning by scoping the accepted input to a US stock ticker, which is not in the schema; it does not discuss format variants, suffixes, or invalid-ticker behavior.

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 the specific resource set — insider trades with fields (who, role, date, buy/sell, shares, price), 3- and 12-month counts, institutional ownership, and largest holders with latest change — plus the source (Nasdaq). The retrieval verb is implicit and no sibling is named to contrast against, but an agent can tell this is insider/ownership data rather than quotes or news.

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?

Provides no when-to-use guidance, no prerequisites, and no exclusions or alternatives (e.g., general quotes, news, financials). The only steer is the implicit 'US stock' scope; otherwise the agent must infer the use case.

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