Skip to main content
Glama

BankRegReports

Schedule 13D/G Beneficial Ownership

sec_13dg
Read-only

Schedule 13D/G filings disclosing ≥5% beneficial ownership of a bank's stock. (Source: SEC Schedule 13D/G.)

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

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=true and openWorldHint=true, so the safety profile is covered. The description contributes the ≥5% ownership threshold and the SEC source, which is genuinely useful domain context, but it says nothing about what filings are returned (dates, pagination, historical range) or whether the response is a list or a single record.

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 compact sentences with no filler; the scope qualifier is front-loaded. The parenthetical source attribution is mildly redundant with the schedule name but harmless.

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 lookup with no output schema, the description covers purpose and domain scope adequately, but leaves open what the result set looks like and whether results are time-bounded or paginated. An agent could call it, but could not predict the return shape.

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 required rssd_id parameter whose description already explains it as a Federal Reserve RSSD id. The description adds no further parameter meaning, so the 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 a specific resource — Schedule 13D/G filings — and adds a clear scope qualifier (≥5% beneficial ownership of a bank's stock), which separates it from generic filing tools. It lacks an explicit verb (list vs. fetch) and does not name a sibling such as sec_form_13f or sec_insider_txns, so an agent must infer the boundary from the schedule name alone.

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 guidance on when to use this tool versus the other SEC-oriented siblings (sec_form_13f, sec_insider_txns, sec_8k_events). The ownership threshold implies a domain, but no conditions, exclusions, or prerequisites are stated.

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