Skip to main content
Glama
Sign In
yfinance-ai MCP server

yfinance-ai MCP server

by lkcair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_insider_transactions

Read-onlyIdempotent

Retrieve recent insider buy/sell transactions for a stock ticker, helping you assess insider sentiment and corporate trading activity.

Instructions

Get recent insider trading activity.

Args: ticker: Stock ticker symbol

Returns: Recent insider buy/sell transactions

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": "get_insider_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only the temporal qualifier 'recent' and that results are buy/sell transactions, which is modest extra context.

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?

Short and front-loaded, with the purpose in the first sentence. The 'Args:' block is largely redundant filler given the parameter name, but it costs little.

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?

An output schema exists, so return values need no explanation. For a one-parameter read tool this is roughly adequate, but 'recent' is undefined (no window/limit) and the overlap with sibling insider tools is unaddressed.

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%, so the description carries the burden for the single parameter. It states 'ticker: Stock ticker symbol,' which is essentially a restatement of the parameter name and adds no format, exchange, or case guidance.

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?

States a specific verb and resource: 'Get recent insider trading activity.' Clear on its own, but it does not distinguish itself from the sibling get_insider_purchases or get_insider_roster_holders, which an agent could easily confuse with this one.

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 when-to-use guidance, no conditions, no alternatives named. With several insider-related siblings (get_insider_purchases, get_insider_roster_holders), the absence of routing guidance is a real gap.

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

Deploy Server

Other Tools