Skip to main content
Glama

BRAINIAC Claims Assist

Analyze a policy and prepare claim evidence

claims_analyze

Extract policy clauses, run a preliminary text-match screen, and build a general evidence checklist. This is not legal advice or confirmation of coverage. Price $0.10 USDC. POST /api/v1/claims/analyze. 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": {
      "fileBase64": "<fileBase64>",
      "incidentType": "<incidentType>",
      "description": "<description>"
    },
    "name": "claims_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameNopolicy.pdf
fileBase64Yes
descriptionYes
incidentDateNo
incidentTypeYes
knownDocumentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well on the commercial/operational side: it discloses the $0.10 USDC price, the POST endpoint, and that unpaid calls return 402 and do not execute. That is genuinely useful pre-call context. It still omits what happens to the uploaded policy file, whether results are stored, and what the response contains.

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, capability stated first, disclaimers and payment terms after. Every sentence adds information; the endpoint line is arguably redundant with typical MCP abstraction but still aids debugging. Nothing is padded.

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 a 6-parameter, 3-required tool with no output schema and no annotations, the description is thin. Because there is no output schema, the description should at least sketch the return shape (clauses found, match results, checklist items), and it should explain the required inputs. Neither is present.

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 6 parameters, so the description must compensate, and it largely does not. 'Policy' loosely maps to fileBase64 and the screen implies incident data, but incidentType, incidentDate, description, filename, and knownDocuments are never explained — notably knownDocuments, whose purpose is entirely opaque from the schema alone.

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 names three concrete actions with specific verbs and resources: 'Extract policy clauses, run a preliminary text-match screen, and build a general evidence checklist.' An agent can tell this is an analysis/screening tool rather than a drafting tool. It does not, however, distinguish itself from claims_validity, which by name alone could plausibly overlap with the validity-screening part.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over claims_validity, claims_letter-draft, or claims_dispute-draft. The only routing signal is the negative disclaimer, 'not legal advice or confirmation of coverage,' which hints this is a preliminary step but never states it explicitly or names an alternative.

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