Skip to main content
Glama
theodor90

form4api-mcp

get_recent_filings

Read-only

Access recent SEC Form 4 insider trading filings. Filter by ticker or browse paginated results.

Instructions

Get the most recent SEC Form 4 filings, optionally filtered by ticker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
tickerNoFilter by stock ticker, e.g. NVDA
per_pageNoResults per page (max 100)
Behavior2/5

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

Annotations already provide readOnlyHint and openWorldHint. Description adds no behavioral traits beyond that; no mention of pagination, data freshness, or limits beyond what's in schema.

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?

Single focused sentence with no fluff. Could add a bit more context about pagination or ordering, but remains efficient.

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?

Adequate for a simple read-only list tool with well-described parameters and annotations, but lacks disclosure of default ordering or result count limits beyond schema.

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%, so baseline 3 applies. Description adds no extra meaning beyond schema descriptions; 'optionally filtered by ticker' is already in schema.

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?

Description clearly states verb (get), resource (SEC Form 4 filings), and optional filter (by ticker). It distinguishes from siblings like get_filing (single filing) and get_insider_transactions (different scope).

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?

Implies usage for recent filings with ticker filter, but does not provide explicit when-to-use or when-not-to-use guidance or mention alternatives among many siblings.

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/theodor90/form4api-mcp'

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