Skip to main content
Glama

SEC 10-K Risk Factor Headings Payment Quote

sec_10k_risk_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/sec/10k-risk (base $0.05; USDC on Base or Polygon); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?cik=320193. To list a company's stated risks: Item 1A risk headings from its latest original 10-K by CIK, as written, grouped by section, with the filing link. Extracted, not rewritten. 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 status below 400). Failed requests are not charged.

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_10k_risk_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 readOnly, idempotent, non-destructive, so the safety profile is covered; the description adds genuinely new behavioral context about charging: errors are not charged on USDC-Base apart from route-noted exceptions, Solana USDC and XRP-ledger RLUSD may charge failed or refused requests, and Polygon native USDC settles only on HTTP status below 400. That is material, non-obvious information for an agent deciding whether to spend. It stops short of saying whether the quoted price can change or expire, and it names Solana/RLUSD settlement rules for chains the quote itself does not offer, which muddies rather than clarifies this specific tool's behavior.

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?

The most decision-relevant line — what the tool is and that it never executes or pays — is front-loaded, which is correct. But the paragraph then sprawls through legal disclaimers ('not financial, investment, tax, legal or health advice,' 'not affiliated with or endorsed by the SEC,' 'not a recommendation to buy, sell or hold') that add little to tool selection, plus settlement rules for Solana and the XRP Ledger that this quote does not support. Roughly half the text is compliance boilerplate rather than selection or invocation guidance.

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?

There is no output schema, so the description must convey what comes back. It describes the risk-heading payload well (headings as written, grouped by section, with a filing link) but never specifies the shape of the payment-terms response itself — price, currency, chain options, or any expiry — which is the tool's nominal primary output. For a zero-parameter, no-output-schema tool where the whole value is the returned quote, that omission is a real gap.

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 has zero parameters, so the baseline is 4. The description does add something beyond the empty schema by showing how the underlying endpoint is invoked ('GET ?cik=320193'), which tells an agent that a CIK is the key input at the HTTP layer even though it is not a parameter here. It does not explain how the agent should supply or vary a CIK given the tool takes none, which is a small remaining gap.

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 description states a specific resource and verb: it returns payment terms for the 10-K risk endpoint and characterizes the underlying payload as 'Item 1A risk headings from its latest original 10-K by CIK, as written, grouped by section, with the filing link.' The opening frames the tool as a pricing/quote tool ('this tool never runs the check or pays'), which is clear once read, but it takes two competing framings (billing quote vs. risk-heading data) before the identity of the tool settles. It does not explicitly contrast itself with siblings such as sec_filings_quote, leaving disambiguation to the names alone.

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 rather than stated: 'this tool never runs the check or pays' and the 'GET ?cik=320193' example signal that this is the pre-payment quote step and that execution happens elsewhere (presumably the 'http' sibling), but the alternative is never named. There are no explicit when-to-use/when-not-to-use conditions, nor a stated prerequisite like 'call this before paying for the 10-K risk endpoint.' An agent can infer the workflow but must do the inferring.

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.