Skip to main content
Glama

BRAINIAC Claims Assist

Draft a claim or dispute letter

claims_dispute-draft

Fill a fixed claim or dispute letter from the caller-supplied facts and the scores from a validity screen. The same fields always produce the same letter. The draft is not sent and it is not a legal filing. Price $0.04 USDC. POST /api/v1/claims/dispute-draft. Unpaid calls return 402 and do not run.

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": {
      "purpose": "<purpose>",
      "claimant": "<claimant>",
      "insurer": "<insurer>"
    },
    "name": "claims_dispute-draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsNo
amountNo
insurerYes
purposeYes
claimantYes
claim_numberNo
incident_dateNo
policy_numberNo
matched_exclusionsNo
claim_validity_scoreNo
risk_of_denial_percentageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses determinism ('same fields always produce the same letter'), that nothing is sent, that it is not a legal filing, the $0.04 USDC price, the POST path, and the 402 failure mode where the call does not run. It omits what the response actually contains (letter text vs. a reference) 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.

Conciseness4/5

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

Five short front-loaded sentences with no filler; the core purpose and the determinism/safety statement come first. The price, endpoint, and 402 detail is operational metadata that crowds out parameter guidance an agent would find more useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with zero annotation coverage, zero schema descriptions, and no output schema, the description leaves too much unstated: per-field meaning, the enum semantics, and the return shape. It covers payment and determinism well but not enough for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% across 11 parameters, so the description must compensate and largely does not. It only gestures at 'facts' and 'scores from a validity screen', leaving the purpose enum (claim vs dispute), matched_exclusions, amount, claim_number, policy_number, and the incident_date format unexplained both in schema and prose.

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?

States a specific verb and resource: fill a fixed claim or dispute letter from caller-supplied facts plus validity-screen scores. It also disambiguates scope by saying the draft is neither sent nor a legal filing, which separates it from a send/file tool. It never names claims_letter-draft, so an agent must infer how this differs from that near-identical sibling.

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 only implied: call this when you have facts and validity scores and want a letter. The description lists operational conditions (price, endpoint, 402 on unpaid calls) but gives no when-to-use versus claims_letter-draft or claims_validity, and no prerequisites such as needing a prior validity screen.

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.

Resources