Skip to main content
Glama

file_claim

Submit insurance claims to Lemonade by providing policy details, incident information, and estimated loss amounts for processing.

Instructions

File a new insurance claim with Lemonade

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
policy_idYesThe policy ID for which to file the claim
claim_typeYesType of claim (e.g., theft, damage, medical)
descriptionYesDetailed description of the incident
incident_dateYesDate of the incident (YYYY-MM-DD format)
estimated_lossNoEstimated loss amount in dollars

Implementation Reference

  • The handler function that implements the logic for 'file_claim' by providing navigation instructions and capturing claim details.
    async function handleFileClaim(args: {
      policy_id: string;
      claim_type: string;
      description: string;
      incident_date: string;
      estimated_loss?: number;
    }): Promise<string> {
      return withBrowser(async (browser, page) => {
        await page.goto(`${LEMONADE_BASE_URL}/claims`, {
          waitUntil: "domcontentloaded",
          timeout: 30000,
        });
        await page.waitForTimeout(1500);
    
        const title = await page.title();
    
        return JSON.stringify({
          status: "action_required",
          message: "Claim filing requires authentication. Please use the Lemonade app or website.",
          claims_url: `${LEMONADE_BASE_URL}/claims`,
          claim_details: {
            policy_id: args.policy_id,
            claim_type: args.claim_type,
            description: args.description,
            incident_date: args.incident_date,
            estimated_loss: args.estimated_loss
              ? `$${args.estimated_loss}`
              : "Not provided",
          },
          instructions: [
            "Option 1 - Lemonade App (Recommended):",
            "  1. Open the Lemonade app on your phone",
            "  2. Tap 'File a Claim'",
            "  3. Follow the AI-guided claims process",
            "",
            "Option 2 - Website:",
            `  1. Visit ${LEMONADE_BASE_URL}/claims`,
            "  2. Sign in to your account",
            "  3. Click 'File a Claim'",
            `  4. Select policy: ${args.policy_id}`,
            `  5. Describe the incident: ${args.description}`,
            `  6. Incident date: ${args.incident_date}`,
          ],
          page_title: title,
        });
      });
    }
  • The schema definition for the 'file_claim' tool.
      name: "file_claim",
      description: "File a new insurance claim with Lemonade",
      inputSchema: {
        type: "object",
        properties: {
          policy_id: {
            type: "string",
            description: "The policy ID for which to file the claim",
          },
          claim_type: {
            type: "string",
            description: "Type of claim (e.g., theft, damage, medical)",
          },
          description: {
            type: "string",
            description: "Detailed description of the incident",
          },
          incident_date: {
            type: "string",
            description: "Date of the incident (YYYY-MM-DD format)",
          },
          estimated_loss: {
            type: "number",
            description: "Estimated loss amount in dollars",
          },
        },
        required: ["policy_id", "claim_type", "description", "incident_date"],
      },
    },
  • src/index.ts:550-552 (registration)
    Registration of 'file_claim' within the tool handler's switch statement.
    case "file_claim":
      result = await handleFileClaim(args as Parameters<typeof handleFileClaim>[0]);
      break;
Behavior2/5

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

No annotations are provided, so the description carries full disclosure burden. While 'File' implies a write operation, the description omits critical behavioral details: whether the action is reversible, what confirmation or claim ID is returned, authentication requirements, or side effects like policy notifications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The single sentence is efficient and front-loaded, but arguably too minimal for a 5-parameter mutation tool with no annotations. It represents under-specification rather than optimal conciseness given the operational complexity.

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 mutation tool handling financial transactions with 4 required parameters and no output schema or annotations, the description is inadequate. It lacks explanation of return values, success/failure behavior, or post-filing workflow that would help an agent handle the response appropriately.

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 description coverage is 100%, documenting all 5 parameters (policy_id, claim_type, description, incident_date, estimated_loss). The description adds no parameter-specific context beyond the schema, which aligns with the baseline score for high-coverage schemas.

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?

The description uses a specific verb ('File') with a clear resource ('insurance claim') and provider context ('with Lemonade'). It effectively distinguishes from siblings like check_claim_status (query vs. create) and contact_support (communication vs. transaction).

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?

The description states what the tool does but provides no guidance on when to use it versus alternatives. It fails to mention prerequisites (e.g., active policy required), preconditions (e.g., verify claim doesn't already exist via check_claim_status), or exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/markswendsen-code/mcp-lemonade'

If you have feedback or need assistance with the MCP directory API, please join our Discord server