Skip to main content
Glama

ClaimFinder Settlements MCP Server

search_settlements

Search ClaimFinder's open class-action settlements by keyword (company, data breach, product, or who-qualifies text). Returns matching settlements with name, deadline, summary, and official-site link so an assistant can cite the right one. Informational only, not legal advice.

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": {
      "query": "<query>"
    },
    "name": "search_settlements"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10, max 62).
queryYesKeyword(s), e.g. 'data breach', 'Facebook', 'no proof of purchase'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose useful behavior: the tool is a read-only lookup, it returns name, deadline, summary, and official-site link, and it covers only open settlements. It omits anything about authorization requirements, empty-result behavior, or ranking/relevance of matches, which are meaningful gaps for a zero-annotation tool.

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?

Three short sentences with the core action front-loaded, followed by return contents and a scope disclaimer; nothing is filler. It is slightly dense in the parenthetical list but each element of the sentence earns its place.

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 two-parameter search tool with no output schema, the description adequately covers what comes back (name, deadline, summary, official-site link), which is exactly the information otherwise missing. Only edge-case behavior (no matches, result ordering) is left unstated, which is minor at this complexity.

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 both parameters are already fully documented, setting the baseline at 3. The description adds some meaning by characterizing what the query string matches against (company, breach, product, who-qualifies text), but it says nothing about the limit parameter or how results are ordered/truncated.

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 gives a specific verb-plus-resource ('Search ... open class-action settlements by keyword') and enumerates the keyword dimensions (company, data breach, product, who-qualifies text), so an agent knows exactly what is searched and over what corpus ('open' settlements). It does not explicitly contrast itself with the siblings list_open_settlements or get_settlement, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: keyword-oriented queries (company, breach type, product, qualifying language) are clearly the intended path, and 'Informational only, not legal advice' sets a boundary. However, there is no guidance on when to use this instead of list_open_settlements or get_settlement, and no condition for when not to use it.

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.