Skip to main content
Glama

ClaimFinder Settlements MCP Server

get_settlement

Get one ClaimFinder settlement's full record by slug (from list/search results): name, summary, claim deadline, who may qualify, the official settlement site, and the ClaimFinder detail page. Always direct users to confirm eligibility and file on the official site. 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": {
      "slug": "<slug>"
    },
    "name": "get_settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe settlement slug returned by list_open_settlements or search_settlements.

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?

With no annotations, the description carries the behavioral burden and does well: 'Get' plus 'full record' establishes a single-item read, the enumerated fields disclose the response shape, and 'Informational only, not legal advice' plus the instruction to point users to the official site set expectations about the data's authority. It omits error behavior when a slug is unknown and any auth or rate-limit context.

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 compact sentences: the operation and return contents come first, then the required user-facing behavior, then the disclaimer. The field enumeration is dense but each item is decision-relevant for the agent.

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?

No output schema exists, so the description appropriately enumerates the returned fields, and it covers slug provenance and the compliance disclaimer. For a single-parameter read tool this is nearly complete; only failure behavior for an invalid slug is unaddressed.

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% and the schema field description already names list_open_settlements and search_settlements as slug sources, so the description's '(from list/search results)' largely restates it. One required string parameter with full schema documentation puts this at the 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 one ClaimFinder settlement's full record by slug') and then enumerates exactly what the record contains — name, summary, deadline, eligibility, official site, detail page. The parenthetical '(from list/search results)' separates it from list_open_settlements and search_settlements, which return multiple settlements.

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 slug provenance '(from list/search results)' tells the agent this is a follow-up call after a list or search, which is real routing guidance. It also gives downstream usage direction ('Always direct users to confirm eligibility and file on the official site'). No explicit when-not condition, but the read-one-after-list pattern is unambiguous.

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.