Skip to main content
Glama

XBRL Financial Facts

sec_facts
Read-only

Most recently filed XBRL concept facts from the bank's 10-K/Q. (Source: SEC EDGAR (XBRL).)

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": {
      "rssd_id": "<rssd_id>"
    },
    "name": "sec_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

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=true and openWorldHint=true, so the safety profile is covered. The description usefully adds the SEC EDGAR source and the 'most recently filed' recency behavior, but it does not explain the shape or scope of returned facts, which is important when no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only one sentence plus a source note, with the key scope front-loaded. There is no unnecessary wording, and the provenance parenthetical is useful rather than filler.

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

Completeness2/5

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

The tool has no output schema, so the description should carry more of the return-value burden. It states what data comes in but not whether facts are returned per concept, with units and periods, or whether only the latest filing is used, leaving the agent with an incomplete picture of the result.

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%, and the only parameter is already documented as a Federal Reserve RSSD id. The description adds no parameter-level meaning beyond the schema, so the baseline score of 3 applies.

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 identifies a specific resource: most recently filed XBRL concept facts from the bank's 10-K/Q. It is distinguishable from sibling filing tools by naming the XBRL concept-facts scope, though it lacks an explicit verb and does not directly name alternatives.

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 phrase 'from the bank's 10-K/Q' implies this tool is for retrieving financial-statement facts from annual and quarterly filings. However, it provides no explicit when-to-use guidance, exclusions, or routing against siblings such as sec_filings or sec_8k_events.

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.

Resources