Skip to main content
Glama

Hsr Party History

hsr_party_history
Read-onlyIdempotent

Get every FTC Hart-Scott-Rodino (HSR) early-termination notice mentioning a given company or fund, oldest to newest, with a total count, a full antitrust-clearance history for that party across every deal the FTC granted early termination on. Example: hsr_party_history({ party: "Carl C. Icahn" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "party": "Carl C. Icahn"
    },
    "name": "hsr_party_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
partyYesCompany or fund name to search for, e.g. "Carl C. Icahn" or "American Securities Partners". Matches anywhere in the notice title (as-filed legal name).
_apiKeyNoOptional, your own api.data.gov key for higher limits; omit to use the shared Pipeworx key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional — your own api.data.gov key for higher limits; omit to use the shared Pipeworx key."New value: +"Optional, your own api.data.gov key for higher limits; omit to use the shared Pipeworx key."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral detail beyond that: results are ordered oldest to newest, a total count is returned, and the output is a full cross-deal clearance history rather than a single notice.

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?

A single front-loaded sentence carries the scope, ordering, and return shape, followed by a compact example. It is a bit run-on with the trailing appositive about clearance history, but no sentence is wasted.

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?

For a two-parameter read tool with no output schema, the description adequately conveys what comes back: notices oldest to newest, a total count, and a full clearance history. Remaining gaps, such as pagination or whether all results are returned for large parties, are minor but not fully addressed.

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% and the schema already explains substring matching against the as-filed legal notice title. The description restates that the parameter accepts a company or fund name and demonstrates it with an example, but adds no matching rules or edge-case semantics beyond the schema.

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

Purpose4/5

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

Names a specific verb and resource: retrieve every FTC HSR early-termination notice mentioning a given party, plus ordering and aggregate count. It is clear what the tool returns, though it never contrasts itself with siblings like hsr_search or hsr_recent, so the agent must infer which party-scoped tool to pick.

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?

Usage is implied by the party-centric framing and the inline example call, so an agent can infer it is for per-company antitrust clearance lookups. There is no explicit when-to-use versus hsr_search/hsr_recent and no statement of exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.