Skip to main content
Glama

SEC Filing Index

sec_filings
Read-onlyIdempotent

SEC EDGAR filing index for one bank's registrant. (Source: SEC EDGAR.)

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

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds only a redundant source attribution (SEC EDGAR, already implied in the first clause) and says nothing about coverage window, pagination, or what an 'index' contains. For an open-world network-backed lookup this leaves meaningful behavior undisclosed.

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

Conciseness3/5

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

The first clause is front-loaded and useful; the parenthetical '(Source: SEC EDGAR.)' repeats information already contained in 'SEC EDGAR filing index' and earns no place. It is short, but short by omission rather than by discipline.

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?

A one-parameter read with no output schema should be easy to specify, yet the description never characterizes the return (list of accession numbers? filing types? dates?). Annotations cover safety, so the gap is narrower than it would otherwise be, but an agent still lacks a clear picture of what it gets back.

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 coverage is 100% and the single parameter rssd_id is fully documented in the schema, so the baseline is 3. The phrase 'for one bank's registrant' adds a marginal clarification that the lookup is scoped to a single institution per call, but no format or constraint details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a concrete resource (SEC EDGAR filing index) and scopes it to one bank's registrant, which is more specific than the title alone. However, it never says whether the result is a list of filings, an index of documents, or metadata, and it does not distinguish itself from siblings such as filings_all or sec_8k_body. The purpose is inferable but not sharply stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no condition for choosing this over filings_all or the form-specific siblings, and no prerequisites or exclusions. The agent must guess from the name alone.

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