Skip to main content
Glama

SEC Filings Payment Quote

sec_filings_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/sec/filings (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 (optional form, limit). Latest SEC EDGAR filings for one company: form, filed date, accession number, primary document URL, 8-K items. GET ticker, optional form, optional limit 1-20. Ticker list and submissions JSON only. 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. Bad input or an unknown ticker: 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 bel

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_filings_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context beyond them: the no-execution guarantee, the $0.02 base price, and an explicit per-chain charging policy ('Bad input or an unknown ticker: Not charged'; Solana/RLUSD may charge on failure; Polygon settles only on success). This is exactly the kind of failure-cost information an agent needs before initiating a paid call, though the final sentence is truncated mid-word ('HTTP status bel') and leaves the Polygon rule 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 a dense wall that repeats the same facts ('USDC on Base or Polygon' appears twice), piles on generic legal disclaimers ('Not financial, investment, tax, legal or health advice'), and is cut off mid-sentence at the end. The genuinely useful content (price, no-execution guarantee, charge-on-failure rules) is scattered rather than front-loaded after the first sentence.

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?

Given zero parameters, no output schema, and a simple quote-returning behavior, the description covers the essentials an agent needs: what is priced, the price, the accepted payment rails, and when a request is or is not charged. The truncation of the Polygon settlement rule and the absence of any description of the returned quote object are the main residual gaps.

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?

For a zero-parameter tool the baseline is 4, but the description actively introduces parameters that do not exist on this tool ('GET ?ticker=AAPL (optional form, limit)', 'optional limit 1-20'), which belong to the downstream HTTP endpoint. That information is useful context about what will be priced, yet it creates a real risk of the agent attempting to pass ticker/form/limit to a schema with no properties.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence identifies the resource specifically ('payment terms for https://horizonpulse.dev/api/sec/filings') and the sibling family ('*_quote' tools) makes the pattern recognizable, but the description then spends most of its length describing the target endpoint's payload ('Latest SEC EDGAR filings for one company: form, filed date, accession number...'), which blurs whether this tool returns a quote or the filings themselves. It is only the isolated clause 'this tool never runs the check or pays' that resolves the ambiguity, and that clause is buried.

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 payment workflow ('Pay the 402 over HTTP with x402 v2'), which tells the agent this is a pricing step preceding a paid HTTP call. However, there is no explicit when-to-use statement and no named alternative among siblings such as sec_company_facts or sec_10k_risk_quote, so the agent must infer that this quote precedes filings retrieval rather than substituting for it.

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.