Skip to main content
Glama

filingspulse

Analyze SEC and international filings with AI plain-language summaries, insider trading signals, and forensic red flag scans. Compare competitors and search full-text filings.

Instructions

FilingsPulse: Global SEC/EDGAR and international filings intelligence API. AI-synthesized plain-language summaries of 10-K, 10-Q, 8-K, S-1/IPO filings. Insider ownership tracking, red flag detection, institutional

Coverage: Global

Endpoints: • exchange ($0.10): Exchange-specific filing intelligence — any listed company worldwide • summary ($0.15): 10-K / Annual Report plain-language summary • insider ($0.10): Insider trading signal — Form 4 analysis • ownership ($0.10): Institutional ownership and 13F analysis • ipo ($0.20): IPO / S-1 prospectus deep dive • 8k ($0.10): Material event analysis (8-K and equivalents) • redflags ($0.15): Forensic accounting red flag scan • compare ($0.15): Side-by-side competitor comparison from filings • search ($0.08): Full-text filing search across all public databases

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNolang
eventNoearnings | executive_change | merger | restatement | debt | cybersecurity | guidance_change
queryNoOptional focus topic (e.g. revenue growth, ESG, M&A)
actionYesWhich endpoint to call. Options: exchange | summary | insider | ownership | ipo | 8k | redflags | compare | search
tickerNoStock ticker (works for US; use company name for international)
companyNoCompany name or local ticker (e.g. LVMH, Samsung Electronics, Tata Consultancy Services)
ticker1Noticker1
ticker2Noticker2
company1Nocompany1
company2Nocompany2
exchangeNoExchange code — enables precise source targeting and jurisdiction-correct filing terminology
date_fromNoYYYY-MM-DD
form_typeNoform_type
Behavior1/5

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

No annotations, and the description fails to disclose any behavioral traits such as rate limits, authentication, destructive actions, or side effects. It includes pricing but no operational details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly long and includes extraneous information such as pricing per endpoint, making it cluttered. It is not front-loaded with the most important information; an AI agent would have to parse through marketing text.

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?

With no output schema and 13 parameters, the description fails to explain how endpoints relate, what inputs are expected for each action, or what the return values are. It is incomplete for an AI agent to use the tool correctly.

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

Parameters2/5

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

Although schema coverage is 100%, many parameter descriptions are mere repetitions of the parameter name (e.g., 'ticker1', 'company1'). Only a few parameters like 'event' and 'action' have meaningful descriptions. The description adds minimal value beyond the schema.

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

Purpose2/5

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

The description positions the tool as an API for SEC/EDGAR filings with multiple endpoints, but it lacks a single clear verb-resource statement. It reads like a product description rather than defining a specific action for an AI agent.

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 on when to use this tool versus the many sibling 'pulse' tools. The description does not differentiate its use case or provide any context for selection.

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/GTCC777/mcp-pulsenetwork'

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