Skip to main content
Glama

ClaimFinder Settlements MCP Server

list_open_settlements

List currently-open U.S. class-action settlements tracked by ClaimFinder — name, claim deadline, a plain-language summary, and who may qualify. Use this to tell a user which settlements they can still file a claim for. Informational only, not legal advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_open_settlements"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax settlements to return (default 25, max 62).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the returned fields, the currently-open-only scope, and an 'informational only, not legal advice' caveat, which is genuinely useful. However, it says nothing about read-only semantics, result ordering, data freshness, or whether the list is truncated, so a simple read-list tool is only partially explained.

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?

Two compact sentences, front-loaded with the resource and scope, followed by the use case and a brief disclaimer. Every clause carries information and nothing is redundant.

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 zero-required-param read-only list tool, the definition covers scope, returned fields, and intended use, and there is no output schema to compensate for. The remaining gap is minor: it does not explain ordering or how the 'limit' interacts with total result count.

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% for the single 'limit' parameter, including default and max values, so the schema already does the heavy lifting. The description adds no meaning about limit or truncation behavior beyond what the schema provides, making the baseline 3 appropriate.

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 and resource ('List ... U.S. class-action settlements') plus the exact scope ('currently-open ... tracked by ClaimFinder') and the returned fields (name, claim deadline, summary, eligibility). The 'currently-open' qualifier implicitly separates it from a filtered search or single-record fetch, though it never names the siblings explicitly.

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 states a concrete use case: 'Use this to tell a user which settlements they can still file a claim for.' That gives clear context for selection, but there is no explicit when-not guidance and no named alternative for cases like searching by keyword or fetching one settlement.

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.