Tanod MCP server

utilpeek: SEC EDGAR company lookup (profile, filings, financials)

sec_company_lookup

Read-onlyIdempotent

Look up a US SEC registrant by ticker or CIK to retrieve company name, identifiers, industry, fiscal year end, recent 10 filings, and optional financial facts.

Instructions

utilpeek: Look up a company in SEC EDGAR by ticker or CIK. For financials per year or quarter use sec_financials. Returns a US SEC registrant by ticker or CIK from SEC EDGAR: name, CIK, tickers, exchanges, SIC industry, state, fiscal year end and the latest 10 filings with links; with include_facts, the latest annual revenue, net income, total assets (USD) and shares outstanding. Informational only, not investment advice. Data: SEC EDGAR (public domain), cached up to 1 hour; no SEC endorsement implied. Send exactly one of ticker or cik; bad input is a 422 and an unknown company a 404 company_not_found (neither charged); an upstream outage is a 503 (not charged). Typically 1-3 s (cached under 0.1 s). Price: USD 0.003. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/sec-edgar-company-filings-api.html

Input Schema

TableJSON Schema

Name	Required	Description
`cik`	No	SEC Central Index Key, 1-10 digits, as a number or a string (leading zeros and a CIK prefix allowed, such as 320193 or 0000320193). Send ticker or cik.
`ticker`	No	Exchange ticker such as AAPL (class shares as BRK-B, BRK.B or BRK/B). Send ticker or cik.
`include_facts`	No	Also return headline XBRL facts: latest annual revenue, net income and total assets (USD) and shares outstanding.

Output Schema

TableJSON Schema

Name	Required	Description
`cik`	No
`sic`	No
`name`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`facts`	No
`stale`	No
`cached`	No
`source`	No
`filings`	No
`tickers`	No
`exchanges`	No
`disclaimer`	No
`facts_note`	No
`cache_seconds`	No
`fiscalYearEnd`	No
`sicDescription`	No
`stateOfIncorporation`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description layers on substantive behavior: caching up to 1 hour, error taxonomy (422 bad input, 404 company_not_found, 503 outage), the fact that error responses are not charged, latency of 1-3s (sub-0.1s cached), pricing, and a free-tier rate limit. It also flags the informational-only disclaimer and no-implied-endorsement constraint.

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-loads purpose and the sibling routing before descending into response fields, errors, latency, price and docs. Dense but well ordered; the pricing/free-tier/docs tail is long, though each element is actionable for an agent that must decide whether to spend a call.

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?

For a read-only lookup with an output schema and full schema coverage, the description covers everything an agent needs: inputs, alternatives, response shape, error semantics, cost, rate limits and data provenance. No material gap remains.

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, but the description adds a genuine constraint not encoded in the schema: exactly one of ticker or cik must be sent. It also hints at accepted CIK formats (leading zeros/prefix), which the schema covers, and clarifies what include_facts adds to the response.

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 and resource ('Look up a company in SEC EDGAR by ticker or CIK') and enumerates the returned fields (name, CIK, tickers, exchanges, SIC, state, FY end, latest 10 filings). It explicitly distinguishes itself from the sibling sec_financials, so an agent can route without opening either schema.

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?

Names the alternative and the condition selecting it: 'For financials per year or quarter use sec_financials.' It also spells out the input contract ('Send exactly one of ticker or cik') and how failures map to 422/404/503. There is no broader when-not-use guidance, but the main routing decision is covered.

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

Deploy Server