Skip to main content
Glama
Sign In

Sec Financial Statements

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Company Financial Facts

company_financial_facts
Read-onlyIdempotent

Dimensioned XBRL facts for one filer — segment, geography or other axis breakdowns that data.sec.gov companyfacts/frames cannot return (those APIs expose undimensioned consolidated totals only). Give a company name (ILIKE match) or a CIK; optionally narrow to one tag (e.g. "Revenues", "LongTermDebtNoncurrent"). Returns each fact's period, value, unit, and — for a dimensioned fact — the segment/member axis it belongs to. Sourced from SEC DERA Financial Statement & Notes data sets, covering only the periods actually loaded (see fsn_coverage).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tag": "Revenues",
      "company": "Apple"
    },
    "name": "company_financial_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK, with or without leading zeros. Takes priority over company if both are given.
tagNoExact XBRL tag name to filter to, e.g. "DerivativeNotionalAmount" (case-sensitive).
limitNoMax facts to return, 1-500 (default 100).
companyNoCompany name, matched with ILIKE (e.g. "Flutter Entertainment"). Omit if passing cik.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so the safety profile is covered. The description adds genuinely non-obvious context: the provenance (SEC DERA FSN data sets) and the hard limitation that only loaded periods are covered, with a pointer to fsn_coverage. Missing only operational details like auth or rate limits.

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 the core differentiator (dimensioned facts vs. undimensioned APIs) and then covers inputs and returns. Efficient overall, though the parenthetical about companyfacts/frames is somewhat dense and the return-value sentence could be tighter.

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?

With no output schema, the description carries the return contract itself — period, value, unit, and the segment/member axis for dimensioned facts — and flags the coverage limitation. Nothing material for correct invocation is missing.

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 all four parameters are already documented in the schema. The description restates the company/CIK alternatives and gives tag examples, adding modest color but no syntax or format information beyond the schema.

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 resource (dimensioned XBRL facts for one filer) with the distinguishing scope spelled out: segment/geography/axis breakdowns that data.sec.gov companyfacts/frames cannot return. An agent can tell this apart from company_facts and tag_cross_company_screen 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 Guidelines4/5

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

Explains the selecting condition clearly — use this when you need dimensioned facts, because companyfacts/frames only expose undimensioned consolidated totals — and points to fsn_coverage for period coverage. It stops short of explicitly naming a sibling tool to use instead for consolidated totals, so it is context-rich but not a full when/when-not/alternative triple.

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

All Sec Financial Statements toolsInspect
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