Skip to main content
Glama

Agent Utility Suite (x402)

by io.github.vanakenj45
OverviewDiscussionsAdmin

SEC 10-K year-over-year changes

sec_section_changes
Read-onlyIdempotent

Answers "What changed in Tesla's risk factors this year?", "Which new risks did Apple add?" or "How did Microsoft's MD&A change since 2022?". Compares one section of a company's 10-K with the same section of an earlier 10-K from SEC EDGAR, paragraph by paragraph: paragraphs added (new risk factors appear here), removed, and edited, each edit with a word-level diff marking deletions [-like this-] and insertions {+like this+}, plus a summary (counts and the share of text unchanged). Moved but identical paragraphs count as unchanged. Defaults to the latest 10-K against the one before it; pass fiscal_year or accession_number for the newer report and compare_to_fiscal_year for the older one (2001 on). Sections: Risk Factors, MD&A, Business, Legal Proceedings, Market Risk, Cybersecurity (filed from late 2023 on). By ticker, CIK or company name, with sec.gov links for both filings. Use it for risk monitoring, due diligence and investment research without reading two 100-page filings. If either report lacks the section 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.04 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).
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.
sectionYesWhich 10-K section to compare: risk_factors, mda, business, legal_proceedings, market_risk or cybersecurity.
fiscal_yearNoThe newer report: the 10-K whose fiscal year ends in this year. Default: the latest 10-K.
accession_numberNoThe newer report as an exact 10-K filing, instead of `fiscal_year`.
compare_to_fiscal_yearNoThe older report to compare against: the 10-K for this fiscal year. Default: the 10-K just before the newer one.

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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), yet the description adds substantial behavioral context beyond them: the billing model (charged only when a result returns, 404 free, 400/5xx not settled), $0.04 USDC via x402, the 'moved but identical counts as unchanged' rule, and the exact diff notation. This is unusually rich disclosure.

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 concrete question examples, then mechanics, then billing. Dense and information-rich, but a few parentheticals and clauses could be trimmed; nothing is truly wasted, though it is longer than strictly necessary.

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?

No output schema exists, so the description carries the return-shape burden and does so: it enumerates added/removed/edited paragraphs, word-level diff markers, and the summary counts plus unchanged-text share. Combined with billing and error behavior, an agent needs nothing else to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description nonetheless adds semantics the schema cannot: the default pairing of latest vs. previous 10-K, the newer/older role of fiscal_year vs. compare_to_fiscal_year, the 2001 floor, and the late-2023 filing boundary for cybersecurity. It adds meaning beyond the structured fields without restating syntax.

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?

Specific verb+resource: compares one 10-K section between two filings paragraph-by-paragraph. The three example questions and the explicit enumeration of outputs (added/removed/edited with diff markers) make it unmistakable against siblings like sec_filing_section, which merely returns a section.

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

Usage Guidelines4/5

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

States intended use cases (risk monitoring, due diligence, investment research) and the default comparison behavior plus the fiscal_year/accession_number/compare_to_fiscal_year selection rules. It does not, however, explicitly name sibling tools (sec_filing_section, sec_filing_sections, sec_full_text_search) as alternatives for narrower needs.

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