Skip to main content
Glama

Officer Filing History (Form 3/4/5)

officers_full
Read-onlyIdempotent

Full officer Form 3/4/5 filing history per filer - every reported owner/role row (director / officer / 10% holder / other) with issuer and period of report. (Source: SEC Form 3/4/5.)

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

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real context beyond that: the source is SEC Form 3/4/5 filings, the output is row-level rather than summarized, and rows carry issuer and period. It is silent on result volume ('every row' suggests potentially large payloads), pagination, or what an empty/missing filer yields.

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?

A single dense sentence front-loads the resource and scope, followed by a short source attribution that earns its place by identifying the underlying dataset. No redundant filler, though the parenthetical source note partially repeats 'Form 3/4/5' already stated in the first clause.

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 carries the burden of describing returns and does so by naming the row fields (owner role, issuer, period of report). For a one-parameter read-only tool this is largely sufficient, with only sibling disambiguation and result-size expectations missing.

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 rssd_id parameter is fully documented as a Federal Reserve RSSD id. The description only reinforces this by saying the history is 'per filer', adding modest meaning without new syntax or constraints; baseline 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 names the specific resource (SEC Form 3/4/5 officer filing history), the scope ('full', 'per filer'), and the row grain (every reported owner/role row with director/officer/10% holder/other roles plus issuer and period of report). It clearly conveys what data comes back, but never contrasts itself with the sibling sec_officers, so an agent cannot tell from the text which one to pick.

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?

'Per filer' combined with the single required rssd_id implies this is the per-filer lookup path, which is usable guidance. There is no explicit when-to-use/when-not statement and no routing to sec_officers or filer_history, so the choice is left 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.

Resources