Skip to main content
Glama

check_claim_status

Check the status of an existing Lemonade insurance claim by providing the claim ID and associated email address.

Instructions

Check the status of an existing Lemonade insurance claim

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claim_idYesThe claim ID to check
emailYesEmail address associated with the claim

Implementation Reference

  • Handler function for the "check_claim_status" tool.
    async function handleCheckClaimStatus(args: {
      claim_id: string;
      email: string;
    }): Promise<string> {
      return withBrowser(async (browser, page) => {
        await page.goto(`${LEMONADE_BASE_URL}/claims`, {
          waitUntil: "domcontentloaded",
          timeout: 30000,
        });
        await page.waitForTimeout(1500);
    
        return JSON.stringify({
          status: "action_required",
          message: "Claim status requires authentication.",
          claims_url: `${LEMONADE_BASE_URL}/claims`,
          claim_id: args.claim_id,
          email: args.email,
          instructions: [
            `1. Visit ${LEMONADE_BASE_URL}/login and sign in with ${args.email}`,
            "2. Navigate to 'My Claims'",
            `3. Find claim ID: ${args.claim_id}`,
            "4. View the current status and any updates",
            "",
            "Alternatively, check your email for claim updates from Lemonade.",
          ],
        });
      });
    }
  • src/index.ts:91-107 (registration)
    Tool registration for "check_claim_status".
      name: "check_claim_status",
      description: "Check the status of an existing Lemonade insurance claim",
      inputSchema: {
        type: "object",
        properties: {
          claim_id: {
            type: "string",
            description: "The claim ID to check",
          },
          email: {
            type: "string",
            description: "Email address associated with the claim",
          },
        },
        required: ["claim_id", "email"],
      },
    },
Behavior3/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. It implies a read-only operation via 'Check' and constrains scope with 'existing', but lacks details on return format, error handling (e.g., claim not found), idempotency, or authentication requirements. Adequate but minimal for a simple status retrieval tool.

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

Conciseness5/5

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

Single sentence of eight words with action verb front-loaded. Zero redundancy or waste. Every word serves the purpose of identifying the tool's function.

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 two-parameter tool without output schema, the description adequately covers the core function but has clear gaps regarding return values (what status states exist), error scenarios, and pagination (if applicable). Minimum viable for the complexity level.

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 has 100% description coverage ('The claim ID to check', 'Email address associated with the claim'). The description reinforces the 'existing' constraint for claim_id but adds no syntax details, format examples, or cross-parameter validation rules (e.g., email must match claim owner). Baseline 3 appropriate when schema does heavy lifting.

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?

Description uses specific verb 'Check' with clear resource 'status of an existing Lemonade insurance claim'. The term 'existing' effectively distinguishes this from sibling 'file_claim' (new claims), while 'status' differentiates it from 'get_documents', 'view_policy', and other siblings.

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 word 'existing' implies this is for previously filed claims, providing implicit context for when to use versus 'file_claim'. However, there is no explicit guidance on when to use this tool versus alternatives, prerequisites, or exclusion criteria (e.g., claim age limits).

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