Skip to main content
Glama

Stratalize Intelligence

Get Ftc Enforcement History

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.6/5.0
Behavior3/5

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

Annotations already establish read-only, open-world, non-destructive behavior. The description adds genuinely useful non-annotation context — that consent orders persist 10-20 years, survive acquisition and bind the acquirer, and that each call costs $0.50 USDC — but says nothing about response shape beyond a single illustrative example, pagination, or coverage limits for companies with no enforcement record.

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?

The when-to-use framing is front-loaded and the penalty/durability facts are compact and decision-relevant. The worked example is longer than strictly necessary and reads slightly promotional, but it is doing real work by previewing return content.

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?

With no output schema, the description must convey return content, and the embedded example (year, civil penalty amount, restriction duration, reporting obligations) does that adequately. The main residual gap is input-format ambiguity for company_name and behavior on no-match results.

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?

There is a single required parameter with 0% schema description coverage, so the description must carry the burden. It implies the input is a company identifier ("for a company") and the example shows a company-name style value, but it never states whether ticker, legal entity name, or fuzzy matching is expected.

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 names the resource (FTC enforcement/consent-order history) and the entity it applies to (a company), and frames it as exposure assessment across antitrust, consumer protection, and data privacy. It is specific enough to distinguish from unrelated siblings, though it never explicitly contrasts with adjacent siblings like get_occ_enforcement_actions or get_litigation_enforcement_snapshot.

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?

It gives concrete trigger conditions: before an acquisition, strategic partnership, or enterprise vendor selection. It does not state when NOT to use it or name an alternative tool for overlapping needs, so it stops short of full routing guidance.

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