Skip to main content
Glama
clousai

Clous MCP server

Official
by clousai

search_beneficial_ownership

Search SEC 13D/13G filings to identify beneficial owners of public companies. Filter by issuer, person, or filing details.

Instructions

Search 13D/13G beneficial-ownership filings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNo
limitNoPage size, 1–100 (default 25).
cursorNoPagination cursor from a prior page's page.next_cursor.
issuerNo
personNo
filed_toNo
cik_filerNo
form_typeNo
filed_fromNo
form_classNoSubstring on form type, e.g. "13D" or "13G".
cik_subjectNo
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'search', implying a read-only operation, but does not mention pagination behavior, required filters, or whether the operation is safe. This lack of detail is a significant gap.

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?

The description is one short, front-loaded sentence with no wasted words. However, it is terse to the point of under-specification, though that is more of a completeness issue than a conciseness one.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 11 parameters, no output schema, and no annotations, a one-sentence description is grossly insufficient. It does not explain return values, filtering options, or how to use the many parameters, making it inadequate for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no parameter information. Schema coverage is only 27%, leaving 8 of 11 parameters undocumented in the schema. The description does nothing to compensate for this low coverage, providing zero insight into parameters like issuer, person, or filed_from.

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 clearly states the tool searches for 13D/13G beneficial-ownership filings, which is a specific verb and resource. This distinguishes it from general search tools like search_filings, though it does not explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus the many sibling search tools, nor any conditions or prerequisites. The description only states the action without context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/clousai/Mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server