Skip to main content
Glama
ER-EPR

futu-opend-mcp

by ER-EPR

get_insider_data

Access US insider holdings and trades (Form 4) for any stock. Select holder list or trade list by data type.

Instructions

US insider holdings/trades - 内部人持股/内部人交易/高管交易/Form 4. US stocks only. data_type: holders (insider holder list) or trades (insider trade list).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNo
codeYes
data_typeYes
holder_idNo
Behavior2/5

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

No annotations exist to cover behavioral traits. The description does not mention authorization, rate limits, or what happens if no data is found. It lacks any behavioral context beyond the data type options.

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 concise with two sentences plus a bilingual label. It front-loads the purpose in English. The Chinese translation adds no value for an English-oriented AI but does not harm conciseness.

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

Completeness2/5

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

Given 4 parameters, no output schema, and no annotations, the description is insufficient. It omits details on num, holder_id, and return format, and does not clarify how results are structured or paginated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 4 parameters with 0% description coverage. The description explains data_type (holders/trades) and implies code is a US stock symbol, but num and holder_id are not described. This partially compensates but leaves significant gaps.

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 retrieves US insider holdings/trades (Form 4) and specifies US stocks only. It distinguishes from siblings like get_institutional_holdings by focusing on insiders and mentioning Form 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates US stocks only and defines data_type options, but provides no guidance on when to use this tool versus alternatives (e.g., get_holder_detail) or when it is not appropriate.

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/ER-EPR/futu-opend-mcp'

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