Skip to main content
Glama

Sec Form D

by io.github.pipeworx-io

Form D Amendment Chains

form_d_amendment_chains
Read-onlyIdempotent

Group one issuer’s recent Form D notices into original-plus-amendment chains using each filing’s previous accession number. This prevents amendments from being mistaken for separate raises; incomplete SEC recent history can leave a chain without its original.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikYes
limitNoFilings to inspect (1-20, default 20).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikYes
chainsYes
issuer_nameNo
interpretationYes
returned_chainsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint/idempotentHint; description adds nuance about chain completion - incomplete SEC history causing missing originals, and implies grouping logic.

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

Conciseness5/5

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

Two sentences with no filler; front-loaded purpose and caveat, efficient and clear.

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

Completeness4/5

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

Adequately describes grouping logic and a key limitation. Output schema exists but not shown, so return value details are not missed. Still could mention output structure briefly.

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?

Description provides no parameter details. Schema covers only 50% (limit has a description, cik does not). The description lacks compensation for the undocumented cik parameter.

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?

Clearly states the tool groups Form D notices into chains using previous accession numbers, distinguishing it from sibling tools like form_d_issuer_history or form_d_recent_raises by focusing on amendment tracking.

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

Usage Guidelines4/5

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

Explains the benefit (prevents mistaken separate raises) and warns about incomplete history, but doesn't explicitly compare to alternative tools like form_d_recent_raises for raw filing lists.

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

All Sec Form D toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Many tools have overlapping purposes, e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded all route questions to data sources with minor differences. Form D tools and meta-tools (discover_tools, suggest_questions) further blur boundaries, making it hard for an agent to select the right tool.

Naming Consistency4/5

Most tools follow a consistent snake_case verb_noun pattern (e.g., resolve_entity, validate_claim, subscribe). However, there are minor deviations like bet_research and deep_research without clear verbs, and the ask_pipeworx variants use irregular suffixes.

Tool Count2/5

With 39 tools, the server is over-scoped, including many utility and meta-tools (remember, recall, forget, list_subscriptions) that inflate the count beyond the core domain (SEC Form D and data lookups). A more focused set of 10-15 tools would be more coherent.

Completeness4/5

The tool set covers a very broad range of data sources and actions, including SEC filings, prediction markets, entity profiling, and AI visibility. However, the completeness is uneven; for example, there are many Form D tools but few for other SEC forms, and some areas like weather or clinical trials are only accessible via ask_pipeworx.

Resources