Skip to main content
Glama

Agent Utility Suite (x402)

by io.github.vanakenj45
OverviewDiscussionsAdmin

SEC 10-K / 10-Q sections, several at once

sec_filing_sections
Read-onlyIdempotent

Answers several questions about one report at once, e.g. "What are Nvidia's risks, and what does management say about results?". Returns 2 or 3 sections of the same 10-K or 10-Q from SEC EDGAR as clean text, in one call: Risk Factors, MD&A, Business, Legal Proceedings, Market Risk, Cybersecurity. Same inputs and output per section as sec_filing_section (latest filing, a fiscal_year since 2001, or an exact accession_number; by ticker, CIK or company name), at $0.015 for up to three sections instead of $0.01 each. Sections the filing does not contain are listed in not_found; if none can be read you get 404, free. You are only charged when a result is returned: invalid input (400) and upstream failures (4xx/5xx) are not settled. Costs $0.015 USDC per call via x402. Paid per call with x402 inside MCP (see the server instructions).

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key, e.g. 320193. Use this, `ticker` or `company`.
viaNoOptional: the tool whose next_calls suggested this call (filled in for you).
formNoAnnual report (10-K, the default) or quarterly report (10-Q). With `accession_number`, taken from that filing.
tickerNoUS stock ticker, e.g. AAPL, MSFT, BRK-B. Use this, `cik` or `company`.
companyNoCompany name, e.g. "Apple" or "Coca-Cola". Use this, `ticker` or `cik`; a name matching several companies returns their tickers, free.
sectionsYes2 or 3 sections to read from the same filing: risk_factors, mda, business, legal_proceedings, market_risk, cybersecurity. Business and cybersecurity exist only in 10-Ks.
fiscal_yearNoReturn the report whose fiscal period ends in this calendar year instead of the latest one, e.g. 2022 for Apple's 10-K for the year ended September 24, 2022. For a 10-Q, the latest quarter ending in that year. EDGAR has HTML filings from 2001 on.
accession_numberNoReturn the section from this exact 10-K or 10-Q filing of the company, e.g. 0000320193-22-000108.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / via
      Added value: +{
+  "description": "Optional: the tool whose next_calls suggested this call (filled in for you).",
+  "maxLength": 64,
+  "type": "string"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the exact billing model ($0.015 per call, cheaper than per-section), that 404 on no-readable-sections is free, and that 400/upstream 4xx-5xx are not settled. It also documents the `not_found` behavior for sections absent from the filing and the x402 payment requirement — all operationally material context the annotations do not carry.

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?

Front-loaded with purpose and an example, then inputs, then pricing/error semantics — a sensible order. It is dense and mostly earns its length, but the payment mechanism is stated twice ('Costs $0.015 USDC per call via x402' and 'Paid per call with x402 inside MCP'), which is redundant.

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?

There is no output schema, so the description carries the return burden — it specifies clean text, 2-3 sections, the `not_found` list, and the 404 case. Combined with the cost/error behavior and the per-section equivalence to sec_filing_section, an agent has everything needed to call and interpret this tool.

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 description coverage is 100%, so the baseline is 3. The description largely restates schema semantics (latest filing default, `fiscal_year` since 2001, exact `accession_number`, ticker/CIK/company) and its 'Business and cybersecurity exist only in 10-Ks' note duplicates the schema's enum description rather than adding new syntax or format detail.

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

Purpose5/5

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

States a specific verb+resource+scope: returns 2-3 named sections of the same 10-K/10-Q, with the exact section list enumerated. It explicitly distinguishes itself from the sibling sec_filing_section ('Same inputs and output per section as sec_filing_section... at $0.015 for up to three sections instead of $0.01 each'), so an agent can route between the two without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with the selecting condition — answering several questions about one report at once, with a worked example — and names the alternative (sec_filing_section) plus the economic reason to pick this one. Implicit exclusions are also clear: it is per-filing, so multi-company or multi-filing needs go to the batch/single sibling.

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

All Agent Utility Suite (x402) toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources