Skip to main content
Glama

Professor Sausages — Finance

by com.professorsausages

SEC filing sections (10-K / 10-Q / 8-K)

sec_filing_section

Parsed sections of a SEC filing by ticker or CIK: 10-K (default), 10-Q, or 8-K. Sections like business, risk_factors, mdna. Corpus 2015→now; missing filings can be requested via request_data. Example: {ticker:'AAPL', selector:'2023', sections:'risk_factors,mdna'}. Paid: call without x_payment to receive this call's exact terms (amount, asset, network), sign them, then call again with x_payment. The free pricing tool lists every price at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formNoWhich filing form to fetch.10-K
tickerYesTicker symbol or 10-digit CIK
sectionsNoComma-separated section keys to include in full, or 'all'. Omit for the manifest only.
selectorNo10-K: fiscal year. 10-Q/8-K: period-end date YYYY-MM-DD or a year. Omit for the latest on file.
x_paymentNoOptional signed x402 payment payload (base64, what the X-PAYMENT header carries). Omit to receive the exact payment terms; sign them (e.g. @x402/fetch) and call again with this argument to settle and get the data.

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden of disclosing behavior. It discloses the paid nature, the payment negotiation flow, the corpus date range (2015→now), and the default form. It doesn't mention error handling or rate limits but covers the most important behavioral trait (payment) well.

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

Conciseness5/5

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

The description is four sentences, front-loaded with the core purpose, then an example, corpus info, and payment instructions. Every sentence earns its place with no redundancy or fluff.

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?

For a tool with 5 parameters and no output schema, the description covers the essential context: forms, default, sections, corpus range, missing-filing alternative, and the paid payment flow. It doesn't explain the 'manifest' concept or return structure, but the intended usage is clear enough.

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 baseline is 3. The description includes an example combining ticker, selector, and sections, but this largely repeats schema examples. The x_payment flow is also described in the schema, so the description adds little beyond what the schema already provides.

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?

The description clearly states the tool provides 'Parsed sections of a SEC filing by ticker or CIK: 10-K (default), 10-Q, or 8-K.' It names specific section types and the input key. It also distinguishes from siblings by noting missing filings go to request_data and pricing is handled by the free pricing tool.

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?

The description explicitly says 'missing filings can be requested via request_data' and 'The free `pricing` tool lists every price at once,' providing when-not-to-use alternatives. It also explains the paid flow: call without x_payment to get terms, then call again with x_payment. This is clear guidance on usage and alternatives.

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

All Professor Sausages — Finance toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct resource and operation: coverage and pricing are meta, find_data searches endpoints, request_data handles missing data, and the data tools are clearly separated by type (FX, holdings, insider, IPO, macro, SEC filings, security holders). Even the three holdings-related tools have clear boundaries: manager_holdings gives a portfolio, holdings_changes gives changes vs prior quarter, and security_holders gives holders by CUSIP.

Naming Consistency3/5

All names use lowercase with underscores, which is consistent, but the pattern mixes nouns (coverage, pricing, fx_rate, macro_series) and verb_noun pairs (find_data, request_data). This is readable but not a fully predictable verb_noun convention as seen in well-structured servers.

Tool Count5/5

With 12 tools, the count is well within the ideal range for a data-access server, covering discovery, metadata, pricing, and a broad set of financial datasets without feeling bloated.

Completeness4/5

The domain is financial data access, and it covers key areas: SEC filings, institutional holdings, insider activity, IPO pipeline, macroeconomic series, FX rates, and data discovery. The main gap is a lack of a full-text filing retrieval tool, but sec_filing_section provides sections, and request_data allows filling missing coverage.

Resources