Skip to main content
Glama

BRAINIAC Claims Assist

Draft insurer correspondence

claims_letter-draft

Prepare a human-reviewed FNOL, follow-up, or complaint letter. BRAINIAC.software does not send the message or make legal conclusions. Price $0.02 USDC. POST /api/v1/claims/letter-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": {
      "kind": "<kind>",
      "insurer": "<insurer>",
      "summary": "<summary>"
    },
    "name": "claims_letter-draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
insurerYes
summaryYes
claimNumberNo
incidentDateNo
policyNumberNo
requestedActionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries real weight: it discloses that nothing is sent, that no legal conclusions are drawn (a liability boundary an agent needs), the $0.02 USDC cost, the POST endpoint, and that unpaid calls return 402 without executing. That is substantive behavioral context. It still omits what the response contains, whether drafts are persisted, and any idempotency or rate-limit behavior.

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?

Four short sentences, front-loaded with what is produced and immediately followed by the two safety caveats (no sending, no legal conclusions). The pricing and endpoint tokens are compact and functional; the 'BRAINIAC.software' branding adds little but costs one phrase, not a sentence.

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

Completeness3/5

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

For a paid, no-annotation, no-output-schema tool with 7 parameters, the definition covers delivery and billing risks well but leaves the return value undefined — with no output schema, the agent cannot tell whether it receives letter text, a stored draft ID, or a review link. Parameter-level meaning is also absent, so the definition is only partly sufficient.

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 7 parameters, so the description must compensate and largely does not. The letter kinds map loosely to the enum (follow-up ≈ chase), but insurer, summary, claimNumber, incidentDate, policyNumber, and requestedAction get no guidance at all — notably no hint about how much detail 'summary' should carry or how 'requestedAction' shapes the letter.

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 first sentence gives a specific verb (Prepare) and resource (FNOL, follow-up, or complaint letter), and the enum-backed kinds make the scope concrete. It stops short of distinguishing this tool from the sibling claims_dispute-draft, so an agent must still infer the boundary between a 'complaint' letter and a 'dispute' letter.

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?

The description implies usage through the enumerated letter kinds and the 'human-reviewed' qualifier, which tells the agent this is a drafting step rather than an automated send. It never states when to choose this tool over claims_dispute-draft, claims_analyze, or claims_validity, and gives no prerequisites beyond payment.

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