Skip to main content
Glama
theodor90

form4api-mcp

by theodor90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_insiders

Read-only

Search insiders (officers, directors, 10% owners) by name. Searches insiders by name and returns a paginated list of matches with each insider's CIK, title, director/officer/10%-owner flags, and total filing count.

Instructions

Search insiders (officers, directors, 10% owners) by name. Searches insiders by name and returns a paginated list of matches with each insider's CIK, title, director/officer/10%-owner flags, and total filing count. Use this to resolve a person's name to their CIK before fetching their transaction history, career summary, or scorecard — the CIK returned here feeds directly into GET /v1/insiders/{cik}/transactions, /summary, and /scorecard. Omitting the name filter returns insiders in alphabetical order rather than performing a search. limit is accepted as an alias for per_page. Not plan-gated — available on the Free tier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoCase-insensitive substring match against the insider's full name (e.g. "Musk", "cook"). Must be at least 2 characters — shorter values return a 400 QUERY_TOO_SHORT error. Omit to list all insiders alphabetically.
pageNo1-based page number. Defaults to 1.
limitNoAlias for per_page.
per_pageNoNumber of insiders per page. Defaults to 20, maximum 500. `limit` is accepted as an alias; if both are given, per_page wins.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.9.7
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Alias for per_page.",
+  "type": "integer"
+}
    • changedInput schema / properties / per_page / description
      Previous value: -"Number of insiders per page. Defaults to 20, maximum 500."New value: +"Number of insiders per page. Defaults to 20, maximum 500. `limit` is accepted as an alias; if both are given, per_page wins."
  2. Changed3 schema fields changedv1.9.2
    • addedInput schema / properties / name / description
      Added value: +"Case-insensitive substring match against the insider's full name (e.g. \"Musk\", \"cook\"). Must be at least 2 characters — shorter values return a 400 QUERY_TOO_SHORT error. Omit to list all insiders alphabetically."
    • addedInput schema / properties / page / description
      Added value: +"1-based page number. Defaults to 1."
    • addedInput schema / properties / per_page / description
      Added value: +"Number of insiders per page. Defaults to 20, maximum 500."
  3. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint it discloses pagination behavior, the alphabetical fallback when no filter is supplied, the alias precedence rule, the QUERY_TOO_SHORT failure mode, and that the tool is not plan-gated. That is substantial operational context an agent cannot get from the annotations.

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?

Front-loaded with purpose and return contents, then routing guidance, then edge cases in descending priority — zero filler. It is dense at three sentences, but every clause carries information (fields, CIK handoff, omission behavior, alias, tier).

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

Completeness5/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 still enumerates the returned fields and pagination, and it covers the error path, the no-filter fallback, and plan availability. An agent has everything needed to call it correctly and interpret the response.

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 description coverage is 100%, so the schema already documents `name` matching semantics, the 2-character minimum with its 400 error, `page`/`per_page` defaults and maximum, and the `limit` alias. The description restates the alias and omission behavior but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource ('Search insiders') with the entity qualifier spelled out (officers, directors, 10% owners) and the return shape enumerated (CIK, title, flags, filing count). It is clearly separable from siblings like get_insider_directory and get_insider_profile, which return a person given an identifier rather than resolving a name to one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the when-to-use: 'resolve a person's name to their CIK before fetching their transaction history, career summary, or scorecard,' naming the downstream endpoints the CIK feeds. It also documents the degenerate case — omitting `name` returns alphabetical listing rather than searching — so the agent knows not to call it as a plain lister.

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

Deploy Server

Other Tools