Skip to main content
Glama

SEC Insider Transactions Payment Quote

sec_insider_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/sec/insider (base $0.02; USDC on Base or Polygon); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?ticker=AAPL or ?cik=320193 (optional limit 1-10). Recent SEC Form 4 insider transactions for one company: insider and role, date, code, shares, price, shares owned after, filing link. GET ticker or cik, optional limit 1-10. USDC on Base or Polygon. Data from SEC EDGAR; not affiliated with or endorsed by the SEC. Not financial, investment, tax, legal or health advice. Quotes about tokens, securities or other financial products are not a recommendation to buy, sell or hold anything. Unknown ticker, no filings or SEC down: Not charged. On USDC on Base, errors are not charged, apart from the exceptions noted on a route. On USDC on Solana, and RLUSD on the XRP Ledger, a refused or failed request may still be charged. On Polygon (native USDC), a request is settled only when it succeeds (HTTP status below

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sec_insider_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark it read-only, idempotent and non-destructive, and the description adds genuinely new behavioral context: the $0.02 base price, accepted rails (USDC on Base/Polygon), and per-rail charging rules on failure. That charging asymmetry (errors uncharged on Base, possibly charged on Solana/XRPL) is exactly the kind of thing annotations cannot express. The final sentence is truncated mid-clause, so the Polygon settlement rule is left incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is bloated and repetitive: the GET ticker/cik query and the USDC-on-Base/Polygon rail are each stated two or three times, and a long chain of legal disclaimers crowds out the operational content. The trailing sentence is cut off mid-word ('HTTP status below'), which is a structural defect, not just verbosity.

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

Completeness5/5

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

For a pricing/quote tool with no input params and no output schema, the description covers what is needed: price, rails, how the request is formed, what data the paid call returns (insider, role, date, code, shares, price, shares owned, filing link), and what happens on the failure cases. No output schema exists, so the prose has to carry the return-shape burden and does so.

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?

The input schema declares zero properties, so baseline would be 4, but the description introduces GET parameters (ticker, cik, limit 1-10) that are not represented in the schema and are repeated twice. This is useful context about the underlying paid request yet risks an agent trying to pass ticker/cik to the tool itself.

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?

The first clause states a specific verb and resource — it returns payment terms for a named endpoint — and immediately clarifies that it 'never runs the check or pays', which separates it from execution-style siblings like x402_check. It does not, however, name the sibling quote/check tools it should be paired with, and the purpose statement is buried under pricing and disclaimer text.

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 implies the flow (get a quote, then 'Pay the 402 over HTTP with x402 v2') and implicitly draws a boundary against running the check. But there is no explicit when-to-use versus x402_check, x402_check_deep, or sec_filings_quote, and no statement of what an agent should do after receiving the terms.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.