Skip to main content
Glama

Edgrapi — SEC EDGAR Financials

by com.edgrapi.api

Convert SEC XBRL to JSON

get_xbrl
Read-onlyIdempotent

The full XBRL-to-JSON converter. By default returns a company's normalized income statement, balance sheet and cash flow across every reported period, plus a concept index of every us-gaap/dei tag it reports. Pass concept to pull the raw time series for any specific tag(s) beyond the curated fundamentals; pass accession for every concept reported in one specific filing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNoSEC CIK, alternative to ticker.
limitNoMax periods per statement, 1-100 (default 40).
periodNoStatement period (default annual).
tickerNoUS stock ticker, e.g. 'AAPL'.
conceptNoComma-separated us-gaap/dei tag(s) to return the raw series for, e.g. 'Revenues,Assets'. Omit for normalized statements + concept index.
accessionNoAn accession (e.g. '0000320193-24-000123') to return every XBRL concept reported in that one filing. Overrides ticker/concept.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral context: default output spans every reported period, concept mode returns raw time series, and accession mode focuses on one specific filing. This goes beyond what annotations alone communicate.

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?

The description is compact and front-loaded, starting with the default behavior and then layering optional modes. The opening fragment 'The full XBRL-to-JSON converter' is slightly redundant with the title, but the rest of the description earns its place.

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 adequately explains the return shape: normalized statements, concept index, raw series, or per-filing concepts. It also communicates the override semantics for accession and the distinction from curated data. Minor gaps exist around data volume and the cik/ticker precedence, but these are covered by the schema.

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 a baseline of 3 applies. The description adds extra semantic value for `concept` and `accession` by explaining that concept pulls raw time series beyond curated fundamentals and accession captures every concept in a particular filing. This is meaningful enrichment over the schema text.

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 states a specific resource (SEC XBRL filings), a clear conversion action, and the default output: normalized income statement, balance sheet, cash flow, and a concept index. It also distinguishes the tool's modes from related data-pull tools by explaining the optional concept and accession behaviors.

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?

The description gives clear context for when to use default mode versus passing `concept` or `accession`, including the purpose of each mode. It does not explicitly name sibling alternatives or when-not-to-use conditions, so it falls slightly short of a 5.

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

All Edgrapi — SEC EDGAR Financials 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.1/5.0
Disambiguation5/5

Each tool targets a distinct SEC EDGAR resource and action: company info, filings, fundamentals, ratios, insider trades, activist stakes, fund holdings, events, and narrative sections. There is no overlap in purpose, and descriptions clarify any potential ambiguity (e.g., get_activist vs get_holdings).

Naming Consistency5/5

All tools follow a consistent 'get_' prefix followed by a singular or plural noun (e.g., get_company, get_filings, get_ratios). The pattern is uniform and predictable, making it easy to infer behavior from the name.

Tool Count5/5

Nine tools is well-scoped for a financial data server covering company profiles, regulatory filings, and derived metrics. Each tool has a clear, non-redundant role, neither feeling sparse nor bloated.

Completeness4/5

The surface covers the core EDGAR resources: company metadata, filings, financial statements, ratios, insider activity, activist filings, fund holdings, material events, and narrative sections. Minor gaps exist (e.g., direct search for specific filing types or proxy statements), but agents can accomplish most research workflows without dead ends.

Resources