Skip to main content
Glama

Ftc Recent Actions

ftc_recent_actions
Read-onlyIdempotent

Get the most recent FTC enforcement actions (cases and proceedings), newest first, new complaints, settlements, and orders across both competition and consumer-protection enforcement. Optionally restrict to merger enforcement only or non-merger (conduct) enforcement only. Answers "what has the FTC done recently" / "what merger actions has the FTC taken this month." Example: ftc_recent_actions({ days: 30, category: "merger", limit: 10 }).

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": {
      "days": 90,
      "limit": 5,
      "category": "merger"
    },
    "name": "ftc_recent_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back from today to look, by last-updated date. Default 30.
limitNoMax actions to return, newest first. Default 20, max 100.
categoryNoRestrict to merger enforcement, non-merger (conduct) enforcement, or both ("any", the default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the burden is lower. The description adds ordering ('newest first') and the lookback basis ('by last-updated date'), which are useful beyond structured fields, but omits what the returned records look like and any pagination behavior beyond the limit cap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with scope and ordering, then narrowing options, then example triggers. Nothing is wasted and the example mirrors realistic usage.

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, low-complexity listing tool with full schema coverage and annotations, this covers scope, ordering, and filtering adequately. The main gap is that no output schema exists and the description never characterizes the returned records, leaving the agent to guess the response shape.

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 days, limit, and category are already fully documented with defaults and ranges. The description's restatement of the merger/non-merger category and the inline example add little beyond what the schema states, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Get the most recent FTC enforcement actions (cases and proceedings)') plus the content types returned (complaints, settlements, orders) and the enforcement domains covered. The recency-first scope implicitly separates it from ftc_search_cases and ftc_case_detail without ambiguity.

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 when-to-use triggers ('what has the FTC done recently', 'what merger actions has the FTC taken this month') and explains the merge/non-merger scoping choice. It stops short of naming alternatives or stating when not to use it, e.g. for historical lookup or single-case detail.

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.