Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Insider Trading

InsiderTrading
Read-only

Insider Trading: Insider Trading returns recent SEC Form 4 insider transactions for a US public company by ticker - who bought or sold, their role, the number of shares, price and transaction type - plus a derived insider-sentiment summary with net buy/sell activity and cluster-buy detection calculated for you. (Cost: 6 credits)

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

Input Schema

NameRequiredDescriptionDefault
typeNoFilter to open-market buys or sells (buy or sell).
limitNoNumber of transactions to return (1-25). Defaults to 5.
tickerYesStock ticker symbol (e.g. AAPL, MSFT, ADBE)

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful operational context beyond annotations: SEC Form 4 data source, recency, derived sentiment calculations, and a 6-credit cost. It still does not discuss rate limits or data freshness limits.

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 purpose and output contents are front-loaded in one clear sentence, and the cost note is easy to find. However, 'Insider Trading: Insider Trading' is redundant and 'calculated for you' is minor marketing filler.

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?

For a three-parameter, read-only data lookup with an output schema and safety annotations, the definition is nearly complete: it says what data is returned and what it costs. It could be stronger by defining 'recent' or clarifying whether the sentiment summary is always included.

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 100%, so ticker, type, and limit are already documented in the schema. The description reinforces ticker-based lookup and output contents but adds no extra semantics for the type filter or limit parameter, so the baseline 3 is appropriate.

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?

States a specific verb and resource: returns recent SEC Form 4 insider transactions for a US public company by ticker, with named fields and a derived sentiment summary. The Form 4/insider-transaction scope distinguishes it from broader siblings like SECFilings or general stock tools.

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?

Usage is implied by the description: call it for insider buying/selling activity on a ticker. However, it gives no explicit when-to-use guidance, exclusions, or alternatives such as SECFilings or TickerNews.

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

All APIVerve toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources