Skip to main content
Glama

SEC 13F Holdings Changes Payment Quote

sec_13f_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/sec/13f (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 ?cik=1067983 (optional period=YYYY-MM-DD quarter end). 13F holdings changes: latest 13F-HR vs prior per holding (new, exited, increased, decreased), with filing links. 13F data is quarterly, filed up to 45 days after quarter-end, original 13F-HR only, and may not reflect current holdings. 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. 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 stat

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_13f_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 declare readOnlyHint=true, destructiveHint=false, openWorldHint=false — consistent with the description's claim that no network call, payment, or order occurs. The description adds value beyond the annotations: exact price ($0.02 base) and multi-chain payment options, avoiding the need for a second pricing call. It omits the quote's own response shape and validity window, which matters for the follow-up payment flow.

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

Conciseness3/5

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

It is front-loaded well — cost and no-side-effect boundary come first — but the body is bloated: USDC on Base/Polygon is restated three times, and generic financial-advice boilerplate ("not financial, investment, tax, legal or health advice;") is duplicated and dilutes the operational content. The final sentence is also truncated mid-clause, an obvious defect.

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?

For a zero-param quote tool with no output schema, most operational context is present: price, payment rails, data provenance (SEC EDGAR), freshness caveats, and what the underlying dataset contains. Still missing is what the returned quote looks like, how long it is valid, and what an agent should do with it next — the core contract of a quote tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema cannot carry any semantics; the baseline is 4. The description compensates by documenting the query parameters of the paid endpoint (cik=1067983, optional period=YYYY-MM-DD quarter end), which is genuinely useful downstream context not present in 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?

The first clause names the specific resource (payment terms for the https://horizonpulse.dev/api/sec/13f endpoint) and explicitly states the tool's boundary: "this tool does not fetch data, pay, or place orders." The second half describes what the underlying endpoint returns (13F-HR holdings deltas: new, exited, increased, decreased), so an agent can tell it apart from data-returning siblings. What's missing is any explicit contrast with the other *_quote siblings (sec_insider_quote, sec_filings_quote), which the name alone has to carry.

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?

There is real negative guidance ("never runs the check or pays") and an implied alternative: to actually get data you must "Pay the GET request directly over HTTP with x402 v2." However, it never says when an agent should call this quote versus just calling the endpoint, nor whether a quote must precede the paid GET or expires.

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.