Skip to main content
Glama
Johnhyeon

StockLens

by Johnhyeon

get_us_insider

Retrieve US insider trading data including Form 4 filings and net buy summaries for the past 6 months. Use to track insider transactions such as CEO stock sales or purchases.

Instructions

US insider trading — 내부자 거래 Form 4 + 최근 6개월 순매수 요약 (US insider Form 4). "AAPL insider trading", "NVDA 내부자 매수", "CEO stock sale" 같은 질문에 사용합니다.

Args: ticker: US 티커

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns Form 4 filings and a recent 6-month net purchase summary. While not exhaustive, this conveys the key behavioral trait for a simple single-parameter tool.

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 compact and front-loaded with the core purpose. It uses a mix of languages which may slightly reduce clarity, but overall it is efficient and to the point.

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?

Given the tool's simplicity (one parameter, output schema exists), the description covers the essential information: what data is returned (Form 4, net summary) and the parameter meaning. It is adequate for a focused tool.

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?

The schema has a 'ticker' parameter with no description. The tool description adds 'US 티커' (US ticker), providing semantics beyond the schema. For 0% schema coverage, this clarifies the parameter meaning sufficiently.

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 it retrieves US insider trading data, specifically Form 4 and a 6-month net purchase summary. Example queries like 'AAPL insider trading' illustrate usage. This distinguishes it from sibling tools, which focus on prices, financials, or other data.

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?

The description provides example queries that imply appropriate usage scenarios. It does not explicitly state when not to use or offer alternatives, but given no sibling tool covers insider data, the context is clear.

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/Johnhyeon/stocklens-mcp'

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