Skip to main content
Glama

screener_insider_trading

Screen insider trading activity across all stock tickers to identify transactions by corporate insiders, including trade type, shares, and total value.

Instructions

Screen insider trades across all tickers. Returns rows with ticker, name, date, insider_name, relationship, transaction_type, shares, total_value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reqYesScreener request with limit only (no market/region filter).
Behavior3/5

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

No annotations exist, so the description carries full burden. It indicates the tool returns rows with specific fields but does not disclose read-only nature, rate limits, or other behavioral traits beyond output format.

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 concise sentences: first defines action, second lists output columns. No wasted words, and critical information is front-loaded.

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?

For a screening tool with one nested parameter and no output schema, the description is adequate but lacks details on pagination, limit behavior, and any filtering constraints beyond the minimalist schema.

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%, so the description adds little beyond listing output fields. The parameter descriptions in the schema already cover limit and format, and the tool description does not enhance understanding of input parameters.

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?

The description clearly states the tool screens insider trades across all tickers and lists the output columns, making its purpose unmistakable and distinguishing it from other screener siblings.

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?

The description provides no guidance on when to use this tool versus alternatives like insider_transactions_by_ticker or other screener tools, leaving the agent to infer appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ahmetsbilgin/finbrain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server