Skip to main content
Glama
Sign In

trading-signals-mcp

by io.github.gdietsch
OverviewDiscussionsAdmin

SEC Insider Buys (ticker)

insider_buys
Read-only

SEC Form 4 open-market insider purchases (code P) for one ticker: insider, role, shares, price, value, dates, per-insider totals and a cluster flag. From SEC EDGAR. Works with no key (small daily allowance) or with a Trading Signals Toolkit API key (free 100 calls/month, Starter, Pro). Pay-per-call equivalent: $0.01 USDC over x402. Informational only, not investment advice.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLookback in days (1-90, default 30)
tickerYesUS equity ticker, e.g. AAPL or BRK-B

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description goes meaningfully beyond them by naming the data source (SEC EDGAR), the authentication tiers (keyless daily allowance vs. API key at 100 calls/month), the pay-per-call x402 price of $0.01 USDC, and the informational-only disclaimer. It still omits failure behavior for invalid tickers or empty lookback windows.

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?

Front-loaded with the core definition and the returned fields, then compact sentences for source, access tiers, and pricing. The billing/marketing clause ('free 100 calls/month, Starter, Pro') is the least essential element but is short enough not to bloat the text.

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?

With no output schema, the description compensates by listing the returned fields and the cluster flag, plus data provenance and cost model, which is what an agent needs to call and interpret it. The only residual gap is how the days window interacts with the reported per-insider totals.

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%, with both ticker and days fully documented including the 1-90 range and default 30, so the schema carries parameter semantics. The description adds only the notion that exactly one ticker is queried and says nothing about the lookback window, so it does not exceed the baseline.

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+resource+filter: SEC Form 4 open-market insider purchases (code P) for one ticker, and enumerates the returned fields (insider, role, shares, price, value, dates, totals, cluster flag). It is clearly a single-ticker transaction listing, but it does not explicitly contrast itself with the sibling insider_clusters even though it also emits a cluster flag, leaving some ambiguity about which to pick.

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 only implied by the scope words 'for one ticker' and 'code P'. There is no explicit when-to-use statement, no exclusion of other form types or non-open-market codes, and no routing to the alternative insider_clusters tool. An agent must infer the selection rule.

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

All trading-signals-mcp 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