Skip to main content
Glama

SEC Filer History

filer_history
Read-onlyIdempotent

SEC registration / identity change log per filer - registrant CIKs, filing date span, and per-form counts. (Source: SEC EDGAR filing index.)

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": "filer_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 safety is covered. The description adds genuinely useful context by identifying the source as the SEC EDGAR filing index and enumerating what the log contains. It does not disclose what happens when a filer has no SEC registration (empty result?) or how RSSD-to-CIK resolution is performed.

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 payload listed up front and the data source parenthetically trailing. No filler, though the parenthetical source note is the least load-bearing element.

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?

For a one-parameter read tool with no output schema, enumerating the returned fields is valuable and largely sufficient. However, the absence of edge-case behavior (no SEC registration, multiple CIKs, empty history) leaves a gap an agent would hit in practice.

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% with a single documented rssd_id parameter, so the schema carries the burden and baseline 3 applies. The description adds only the framing that results are keyed per filer; it does not explain the RSSD-to-CIK mapping or accepted formats beyond the schema's example.

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 names a specific resource and scope: an SEC registration/identity change log per filer, returning registrant CIKs, filing date span, and per-form counts. This is clearly distinct from filing-listing siblings like sec_filings. It stops short of 5 only because the 'per filer' keying is not tied explicitly to the RSSD id the schema requires.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named despite many SEC siblings. An agent must infer that this is the historical/identity-overview entry point rather than a filing fetch. Usage is only implied by the noun 'history'.

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