Skip to main content
Glama

Ftc Case Detail

ftc_case_detail
Read-onlyIdempotent

Get full detail for one FTC case or proceeding: case status (pending/closed/under order), federal court (if any), the full party caption, the case summary, any linked press release, and the complete document timeline (complaint, orders, settlements, briefs) each with its filing date, document title, and PDF URL. Takes the slug field returned by ftc_search_cases or ftc_recent_actions, the last path segment of the case's ftc.gov URL, e.g. "hims-hers" for https://www.ftc.gov/legal-library/browse/cases-proceedings/hims-hers. Example: ftc_case_detail({ slug: "hims-hers" }).

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": {
      "slug": "hims-hers"
    },
    "name": "ftc_case_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe case's ftc.gov slug (last URL path segment), or the full cases-proceedings URL, either is accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"The case's ftc.gov slug (last URL path segment), or the full cases-proceedings URL — either is accepted."New value: +"The case's ftc.gov slug (last URL path segment), or the full cases-proceedings URL, either is accepted."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds behavioral value by spelling out the shape of the response payload (timeline entries with filing date, title, PDF URL), which is important since no output schema exists; it does not cover failure behavior for invalid slugs.

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?

Front-loaded with the verb and resource in the first clause, then the returned fields, then the parameter origin and derivation, then a concrete example. Every clause carries information; nothing is redundant with the schema or title.

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 single-parameter read-only lookup with no output schema, the description supplies the return-field inventory an agent needs and pins down the parameter format with an example. The only gap is error/empty-result behavior for an unknown slug, which is minor against the otherwise thorough coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description still adds real meaning: it explains that slug is the last path segment of the ftc.gov URL, gives the 'hims-hers' derivation from a full URL, and shows the exact call shape. That goes beyond the schema's own note that a full URL is also accepted, so it earns above the 3 baseline.

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 full detail for one FTC case or proceeding') and then enumerates exactly what detail is returned: status, court, party caption, summary, press release, and document timeline. Sibling differentiation is explicit by naming ftc_search_cases and ftc_recent_actions as the sources of the slug, so the agent can immediately tell this apart from search/list tools.

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?

The description makes clear the tool is used after retrieving a slug from ftc_search_cases or ftc_recent_actions, and gives a concrete call example. It does not explicitly state when not to use it (e.g., that it should not be called with a guessed slug), but the routing context is strong enough that an agent will pick the right tool.

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.