Philadelphia Restoration

check_insurance_coverage

Destructive

Returns Pennsylvania insurance coverage analysis for water and fire damage claims. Evaluates coverage likelihood by HO policy type (HO-1 through HO-6), applies PA-specific regulations including bad faith statute (42 Pa.C.S. § 8371) and Act 119, and provides step-by-step claims process guidance with common denial reasons and appeals strategies.

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": {
      "damage_type": "<damage_type>"
    },
    "name": "check_insurance_coverage"
  }
}

Input Schema

Name	Required	Description
`cause`	No	Specific cause of damage (e.g., 'frozen pipes', 'grease fire')
`damage_type`	Yes	Type of water or fire damage
`policy_type`	No	Homeowner's insurance policy type (default: HO-3)

Schema Changelog

Changes observed during successful MCP inspections.

First observedMar 2, 2026

TDQS

A3.5/5.0

Behavior1/5

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

The description states the tool 'Returns... analysis' and 'provides guidance,' implying a read-only, non-destructive operation. Yet annotations set destructiveHint: true and readOnlyHint: false, which directly contradicts the description. This is a serious inconsistency, so transparency earns the minimum score.

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?

The description is two sentences, front-loaded with the primary purpose, and each clause adds meaningful detail (policy types, PA regulations, process guidance). No filler or redundancy is present, making it concise and well-structured.

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?

The tool has no output schema, so the description must convey what the response contains; it does mention evaluation, regulations, and guidance, but not the return format or structure. The contradictory annotation further undermines completeness. For a relatively complex tool, this is adequate but missing output specifics.

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%, so the baseline is 3. The description adds context around policy_type (HO-1 through HO-6) and damage types, but does not elaborate on the 'cause' parameter beyond the schema. It neither compensates significantly nor falls below the baseline.

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 opens with 'Returns Pennsylvania insurance coverage analysis for water and fire damage claims,' a specific verb and resource that clearly distinguishes this tool from siblings like assess_damage or estimate_cost. It further specifies scope (Pennsylvania) and damage types, leaving no ambiguity about what the tool does.

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

Usage Guidelines4/5

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

The description implicitly scopes usage to 'water and fire damage claims' and indicates it returns coverage analysis, making the intended use clear. However, it does not explicitly exclude alternatives or mention when not to use the tool, so it stops short of a 5.

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

All Philadelphia Restoration tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?