Ridge Pack

Storm damage and leak triage

storm_triage

Read-onlyIdempotent

Triage for storm damage and roof leaks. Gives an urgency of routine, soon or emergency (the same three speeds as Nero Work) with the reasons, safe first steps for the homeowner (no climbing, electrics, bulging ceilings, gas, falling debris, insurer), the temporary cover the roofer should use for each problem (tarpaulin battened over the ridge, tile clips, tingles, flashing tape, cold patch), what to photograph, and a Nero Work job title. Typical call: {"symptoms":["water_coming_through_ceiling","tiles_or_slates_missing"],"missing_count":12,"more_bad_weather_within_24h":true}.

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": {
      "symptoms": "<symptoms>"
    },
    "name": "storm_triage"
  }
}

Input Schema

Name	Required	Description
`trade`	No	Optional. The roofer's own business details (Nero Trade Profile v1). Used to put the contractor on risk notes and to give a stable nero_trade_ref. Not stored by Ridge Pack.
`symptoms`	Yes	What the homeowner sees.
`smell_gas`	No
`raining_now`	No
`missing_count`	No	Roughly how many tiles or slates are missing.
`public_path_or_road_below`	No
`vulnerable_people_in_home`	No	Elderly, disabled, very young or unwell people living there.
`more_bad_weather_within_24h`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the readOnly/non-destructive annotations, the description discloses the tool's substantive output: urgency level with reasons, homeowner-safe first steps, temporary cover guidance, photography list, and a Nero Work job title. This is exactly the behavioral detail an agent needs for a triage tool with no output schema.

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 front-loaded and information-dense, with no filler. The second sentence is a long run-on list, which slightly hurts readability, but every element earns its place.

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?

For an 8-parameter tool with a nested trade object and no output schema, the description supplies strong output context and safety guidance. Gaps remain around several optional boolean inputs and the trade parameter, but the schema covers much of that ground.

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 50%, and the description adds a typical call showing symptoms, missing_count, and more_bad_weather_within_24h. However, it does not explain trade, smell_gas, raining_now, public_path_or_road_below, or vulnerable_people_in_home, so it only partially compensates 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?

The description states a specific verb and resource: 'Triage for storm damage and roof leaks.' It also clearly lists what the tool produces, making the purpose concrete. It does not explicitly differentiate itself from siblings such as weather_window or work_at_height_plan, but the purpose is unambiguous.

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 context for use is clear: storm damage and roof leaks. The typical-call example reinforces when this tool is appropriate. It does not name exclusions or sibling alternatives, but no misleading guidance is present.

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

All Ridge Pack 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.