Access real-time data on the latest mergers and acquisitions with the FMP Latest Mergers and Acquisitions API. This API provides key information such as the transaction date, company names, and links to detailed filing information for further analysis.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default: 0) | |
| limit | No | Limit on number of results (default: 100, max: 1000) |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the transparency burden. It only mentions some output fields (date, company names, filing links) but does not disclose pagination behavior, result ordering, rate limits, or any limitations of the 'real-time' data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-load the purpose and add relevant return-value context. No redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is minimally sufficient for this simple paginated list tool, but since there is no output schema it should more thoroughly describe the return structure. It also omits any relationship to the searchMergersAcquisitions sibling, which would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already fully documents the page and limit parameters, so the description adds no parameter-specific meaning. The baseline of 3 applies because schema coverage is 100%.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Access real-time data') and resource ('latest mergers and acquisitions'). The name and 'latest' phrasing distinguish it from the sibling searchMergersAcquisitions, though no explicit comparison is made.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied: the tool is for retrieving current/latest M&A data. However, it does not explicitly mention when not to use it or direct users to alternatives like searchMergersAcquisitions, so guidance is only implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.