Skip to main content
Glama

get_ftc_enforcement_history

Read-only

Use when evaluating antitrust exposure, consumer protection liability, data privacy enforcement history, or deceptive practices risk for a company before an acquisition, strategic partnership, or enterprise vendor selection. FTC consent orders impose ongoing behavioral restrictions lasting 10-20 years and carry $50,000+ per day penalties for violations. Example: Tech Platform Corp — FTC consent order 2021, $150M civil penalty, 20-year restrictions on data monetization practices, biennial compliance reporting — restrictions survive acquisition and bind acquirer. Source: FTC Enforcement Cases and Proceedings. $0.50 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_name": "<company_name>"
    },
    "name": "get_ftc_enforcement_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely non-structured information: the data source (FTC Enforcement Cases and Proceedings), the pricing ($0.50 USDC per call), and the shape of typical findings (10-20 year behavioral restrictions, $50,000+/day penalties, biennial reporting). It does not cover what is returned when a company has no enforcement record, which is the main remaining behavioral gap.

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-loaded with an explicit 'Use when...' clause, followed by consequence context, a concrete example, and then source and price. The opening sentence is a long run-on enumerating four risk types, and the illustrative example is somewhat verbose, but every block carries useful information.

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

Completeness3/5

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

For a single-parameter read-only lookup with no output schema, the description does most of the work by showing the returned fields via the example and naming the source. However, it omits scope details an agent needs to interpret results — historical coverage range, whether subsidiary/parent names are resolved, and the empty-result behavior.

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 0% for a single required parameter, company_name, and the description offers no format guidance (legal entity name vs. ticker vs. parent/subsidiary, handling of former names). The example implies a company-name lookup, so the meaning is inferable, but the description does not compensate for the empty schema documentation.

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?

The description never states a clean verb+resource sentence, but the use-case framing plus the 'Tech Platform Corp — FTC consent order 2021, $150M civil penalty, 20-year restrictions...' example make clear this returns FTC enforcement actions and consent orders for a named company. It is distinguishable from siblings like get_occ_enforcement_actions or get_fda_recall_history by its FTC/antitrust and consumer-protection domain, though the differentiation is by domain vocabulary rather than explicit contrast.

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 triggering contexts: antitrust exposure, consumer protection liability, data privacy enforcement, deceptive practices risk, and specifically before an acquisition, strategic partnership, or vendor selection. It also explains why it matters ('restrictions survive acquisition and bind acquirer'). No explicit exclusions or named alternatives, so it stops short of a 5.

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.

Resources