Skip to main content
Glama

get_sec_beneficial_ownership

Read-only

Schedule 13D/13G beneficial ownership filings — identifies activist (13D) or passive (13G) 5%+ shareholders with intent classification. Returns activist signal. Source: SEC EDGAR. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.10 USDC per call.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_sec_beneficial_ownership"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: the EDGAR provenance, the concrete deliverable ('returns activist signal'), a per-call cost of $0.10 USDC, and a cryptographic attestation with a verification URL. It stops short of describing coverage windows, filing recency, or response shape.

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 purpose is correctly front-loaded in the first two clauses, but the tail spends a full sentence on promotional-sounding attestation language ('post-quantum signed settlement receipt') that carries little decision value for tool selection. Cost and source earn their place; the verification pitch is padded relative to the signal it provides.

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 annotations and no output schema, the description covers source, output signal, cost, and verifiability. The gaps that matter for correct invocation remain: the sole input (ticker) is never addressed, and there is no indication of what a returned 'activist signal' contains or how historical filings are represented.

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?

There is one required parameter with 0% schema description coverage, so the schema offers only the name 'ticker' and a maxLength of 20. The description implies single-company lookup through the 5%+ shareholder framing but never mentions the ticker, format expectations (exchange suffix, CIK vs symbol), or behavior on unknown symbols.

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 states a specific resource and verb: Schedule 13D/13G beneficial ownership filings, identifying activist (13D) versus passive (13G) 5%+ shareholders with intent classification. An agent can tell what it gets back. It does not, however, distinguish itself from closely related siblings such as get_sec_insider_trading or get_13f_holdings_delta.

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?

Usage is only implied by the subject matter — an agent can infer it is for detecting activist stakes or large passive holders. There is no explicit when-to-use statement, no exclusions, and no named alternative for the adjacent insider-trading or institutional-holdings questions, so routing between siblings 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