Skip to main content
Glama
Sign In
Trading Signals MCP

Trading Signals MCP

by gdietsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

SEC Insider Buys (ticker) ($0.01)

insider_buys
Read-only

Retrieve SEC Form 4 open-market insider purchases for a ticker, including insider roles, shares, prices, values, dates, totals, and cluster flags.

Instructions

Price: $0.01 USDC per call on Base, paid automatically via x402 from X402_PRIVATE_KEY. 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. Failed calls (4xx/5xx) are not charged. 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 observedv0.1.1

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the payment model ($0.01 USDC on Base via x402 from X402_PRIVATE_KEY), that failed 4xx/5xx calls are not charged, and that data originates from SEC EDGAR. It also enumerates the response contents (insider, role, shares, price, value, dates, per-insider totals, cluster flag), which matters since no output schema exists. The 'informational only, not investment advice' disclaimer adds appropriate framing for a read-only data 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?

A tight, information-dense block with no filler; every clause carries cost, scope, output, or caveat information. Leading with pricing before purpose is slightly awkward for an agent scanning for capability, but it is efficient overall.

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 two-parameter paid read tool with no output schema, the definition covers cost, billing failure behavior, data source, and returned fields — enough to call it correctly. Minor gaps remain: no statement of what happens when no purchases exist or any result-count/pagination limits.

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 coverage is 100%, with both ticker and days fully documented in the schema, so the baseline applies. The description adds only the phrase 'for one ticker', which reinforces single-ticker semantics but contributes no format or defaulting detail beyond the schema.

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 precise verb and resource: SEC Form 4 open-market insider purchases (code P) for a single ticker, and enumerates the returned fields. An agent knows exactly what data comes back. It does not, however, distinguish itself from the sibling insider_clusters, even though its own 'cluster flag' output overlaps that territory.

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?

Scope is implied clearly ('for one ticker', with the schema's 1-90 day lookback), so an agent can infer this is a single-ticker lookup. There is no explicit when-to-use/when-not-to-use guidance and no routing to alternative tools such as insider_clusters or event_gate, leaving selection to inference.

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