Skip to main content
Glama

Hsr Search

hsr_search
Read-onlyIdempotent

Search FTC Hart-Scott-Rodino (HSR) early-termination notices by acquirer or target company name. Matches against the notice title, which embeds both parties and the transaction number, so a partial or one-sided company/fund name finds every notice that mentions it. Use this to check "did this merger get antitrust clearance" or "has the FTC granted HSR early termination for this deal." Example: hsr_search({ party: "Blockbuster", limit: 25 })

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": "Blockbuster"
    },
    "name": "hsr_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax notices to return, newest first. Default 25, max 100.
partyYesCompany or fund name to search for, e.g. "Blockbuster" or "Carl C. Icahn". Matches anywhere in the notice title (as-filed legal name, so include known fund suffixes like "L.P." if a plain name misses).
sinceNoOptional, only return notices on or after this date, YYYY-MM-DD.
_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. Changed2 schema fields 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."
    • changedInput schema / properties / since / description
      Previous value: -"Optional — only return notices on or after this date, YYYY-MM-DD."New value: +"Optional, only return notices on or after this date, YYYY-MM-DD."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description still adds real behavioral value by explaining that matching happens against the notice title, which embeds both parties and the transaction number, so a partial or one-sided name still finds all related notices. It does not mention rate limits or what the response looks like, though the apiKey parameter partly covers quota concerns.

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?

Front-loads the resource and scope, then the use cases, then a compact example, with no filler sentences. The matching-semantics sentence is slightly long but earns its place; nothing reads as padding.

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 read-only search tool with four well-documented parameters and no output schema, the description covers purpose, selection context, and matching behavior adequately. The main gap is that it never says what a returned notice contains or how results are ordered, though the limit field supplies newest-first ordering.

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 every parameter including limit defaults, since, and _apiKey is already documented in the schema. The description reinforces that partial or one-sided names work, but that thought is already present in the party field description (as-filed legal name, fund suffixes). Baseline 3 is appropriate.

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?

States a specific verb and resource: search FTC Hart-Scott-Rodino early-termination notices by acquirer or target name. That is far more informative than the title alone. However, it never distinguishes itself from siblings hsr_recent, hsr_party_history, or hsr_coverage, all of which appear to operate on the same notice corpus, so the agent must still guess among them.

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?

Gives concrete use cases in plain language ("did this merger get antitrust clearance", "has the FTC granted HSR early termination for this deal") plus a worked example call, which is clear context for selecting the tool. It stops short of exclusions or naming an alternative for adjacent needs such as recent-only or party-history lookups.

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.