Skip to main content
Glama

BRAINIAC Claims Assist

Score claim validity against exclusions

claims_validity

Match a caller-supplied incident to policy exclusions, dates, and the limit. The validity score falls when an exclusion's distinctive words appear in the incident, and the denial risk rises with those matches. This is a text screen, not a claim decision. Price $0.04 USDC. POST /api/v1/claims/validity. 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": {
      "incident": "<incident>",
      "policy": "<policy>"
    },
    "name": "claims_validity"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyYes
incidentYes

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, the description carries the full load and does well: it discloses the pricing ($0.04 USDC), the endpoint, and critically the failure mode (unpaid calls return 402 and do not run). It also explains the scoring mechanic — exclusion keyword overlap lowers validity and raises denial risk. What it omits is the output shape and the score scale.

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 sentences, front-loaded with purpose and the scoring rule before the operational details. The literal endpoint path is marginally redundant, but nothing else is padded.

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?

Payment and failure behavior are covered, but for a tool with zero annotation coverage, no output schema, and a nested anyOf input, the description should say more about what comes back (score range, denial-risk representation) so an agent can interpret results. It is adequate on invocation, thin on interpretation.

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% and the schema is a complex anyOf of string-or-object for both parameters. The description only gestures at exclusions, dates, and limit, leaving perils, amount, loss_type, notice_on, occurred_on, and the entire string-vs-object duality unexplained. It does not compensate for the coverage gap.

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 concrete verb and resource — matching an incident against policy exclusions, dates, and limit — and the title reinforces the scoring function. The line 'This is a text screen, not a claim decision' implicitly separates it from the heavier claims_analyze sibling without naming it.

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 'text screen, not a claim decision' caveat signals when this tool is insufficient and a deeper analysis is needed, which is useful scoping. However, no alternative tool is named and there is no explicit when-to-use trigger beyond the general matching framing.

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