Philadelphia Restoration

assess_damage

Destructive

Returns structured damage assessment for water and fire damage in Philadelphia residential properties. Classifies 13 damage types by severity, provides prioritized immediate safety actions, estimates restoration costs with Philadelphia market rates, and includes neighborhood-specific risk context. Based on IICRC S500/S520/S700 standards and field experience from Philadelphia restoration companies.

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": "assess_damage"
  }
}

Input Schema

Name	Required	Description	Default
`damage_type`	Yes	Type of water or fire damage to assess
`neighborhood`	No	Philadelphia neighborhood (e.g., 'fishtown', 'center-city')

Schema Changelog

Changes observed during successful MCP inspections.

First observedMar 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

The description adds useful context about standards and content, but it fails to address the annotation destructiveHint=true. While it says 'returns' an assessment, it does not clarify whether the tool has side effects or what might be destructive, leaving an important transparency gap for a mutation-flagged tool.

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?

The description is compact and front-loaded with the main purpose, followed by key details. It is slightly dense but every sentence contributes; the standards citation adds credibility without excessive length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by summarizing the outputs: severity classification, prioritized safety actions, cost estimates, and neighborhood risk. It is sufficiently complete for a two-parameter tool, though it omits any mention of side effects or when to avoid using it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning by stating the tool classifies 13 damage types, which corresponds to the damage_type enum, and mentions neighborhood-specific risk context for the neighborhood parameter, going beyond the schema descriptions.

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 clearly states the tool 'returns structured damage assessment' for water and fire damage in Philadelphia residential properties, naming a specific verb, resource, and scope. It distinguishes itself from siblings like estimate_cost and get_emergency_steps by positioning itself as a comprehensive assessment that includes those aspects.

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?

No explicit when-to-use or when-not-to-use guidance is provided. It does not mention alternatives or exclusions, despite sibling tools like estimate_cost and get_emergency_steps that overlap with the described functionality. Usage context is only implied.

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?