Skip to main content
Glama

FinanceQuery

SEC EDGAR XBRL Facts

get_edgar_facts
Read-onlyIdempotent

Get SEC EDGAR XBRL structured financial data (all reported accounting concepts) for a company. Requires EDGAR_EMAIL env var.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_edgar_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum data points per concept per page; omitted = curated default (25). Applied uniformly across every returned concept.
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated GraphQL sub-fields to include per concept (e.g. "concept,dataPoints"); omitted = curated default set
symbolYesStock ticker symbol (e.g., "AAPL", "MSFT", "TSLA")
conceptsNoComma-separated XBRL concept names to filter to (e.g. "Revenues,Assets"); omitted = curated defaults (headline financials)
taxonomyNoXBRL taxonomy (default: "us-gaap"); also try "ifrs-full" or "dei"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely new operational fact, the EDGAR_EMAIL environment requirement, but says nothing about pagination behavior despite a cursor parameter, or about rate limits and upstream data latency.

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?

Two short sentences with the core purpose front-loaded and no filler. The brevity is efficient, though for a six-parameter paginated tool it borders on under-specification rather than ideal density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, GraphQL-style field selection and pagination, plus no output schema, the description covers only the purpose and one prerequisite. The schema carries parameter detail, but the description does not prepare the agent for paginated, per-concept response traversal or what the returned concepts look like.

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 every parameter including limit, cursor, fields, concepts and taxonomy is already documented in the schema. The description adds no additional parameter meaning, which is acceptable at full coverage but earns only the baseline.

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?

States a specific verb and resource: retrieve SEC EDGAR XBRL structured financial data (reported accounting concepts) for a company. It is clear what the tool returns, but it does not explicitly distinguish itself from the sibling get_financials, which an agent may reasonably consider for financial data.

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?

The description implies when this tool applies (raw XBRL concept data) and adds a concrete prerequisite, the EDGAR_EMAIL env var, which is actionable. It gives no explicit when-not guidance or comparison to get_financials or get_edgar_submissions, leaving the choice to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.