Tlacuilo

sec_facts

sec_facts

Read-only

Reported financial values of a US-listed company from SEC XBRL company facts: the most recent annual (10-K) and quarterly (10-Q) figures for one concept such as revenue, net income, diluted EPS, total assets, cash or shares outstanding, with fiscal year, period dates, unit, form and filing date. Accepts friendly aliases or any us-gaap/dei concept name. Source: SEC EDGAR. Price: $0.005 USDC per call (x402).

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_facts"
  }
}

Input Schema

Name	Required	Description
`cik`	No	SEC Central Index Key, up to 10 digits
`limit`	No	Periods to return per series, 1-40 (default 8)
`ticker`	No	Stock ticker, e.g. MSFT (ticker or cik is required)
`concept`	No	Alias (revenue, net_income, eps, eps_basic, assets, liabilities, equity, cash, shares, operating_income, gross_profit, operating_cash_flow, rd, long_term_debt) or XBRL concept such as Assets or dei:EntityPublicFloat (default Revenues)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the data source (SEC EDGAR) and an explicit price of $0.005 USDC per call via x402, which an agent needs before invoking a paid endpoint. It does not cover failure behavior (invalid ticker/CIK) or result volume, keeping it short of a 5.

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?

One dense sentence that front-loads the resource and scope, followed by the source/price line. Every clause carries information, though the single sentence is long and could have broken the returned-fields list into its own clause for readability.

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?

With no output schema, the description compensates by enumerating what comes back (fiscal year, period dates, unit, form, filing date) and noting the per-series limit default. It is nearly complete for a single-concept fact lookup; only error and multi-series behavior are unaddressed.

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 enum-like alias list, CIK format, and limit range are already documented in the schema. The description largely restates the alias examples and the concept parameter, adding only the note that any us-gaap/dei concept name is accepted, which the schema also states.

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 opens with a specific verb and resource ('Reported financial values ... from SEC XBRL company facts') and narrows scope to the most recent 10-K and 10-Q figures for a single concept. This makes it clearly distinguishable from a filings-retrieval tool, though it never names a sibling to route against.

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 by the scope statement: pull one metric (revenue, net income, diluted EPS, assets, cash, shares) for one US-listed company. There is no explicit when-to-use versus when-not guidance and no mention of when to prefer a filings tool instead.

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

All Tlacuilo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?