Skip to main content
Glama

OpsRev Roofing AI

Calculate Hover recommended roof waste factor

hover_get_roof_waste_factor
Read-only

Compute Hover’s algorithmic Recommended Roof Waste Factor (%) from roof square footage and linear roof measurements.

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": {
      "roofSquareFeet": "<roofSquareFeet>",
      "stepFlashingLinearFeet": "<stepFlashingLinearFeet>",
      "rakesLinearFeet": "<rakesLinearFeet>",
      "valleysLinearFeet": "<valleysLinearFeet>",
      "hipsLinearFeet": "<hipsLinearFeet>"
    },
    "name": "hover_get_roof_waste_factor"
  }
}

Input Schema

NameRequiredDescriptionDefault
hipsLinearFeetYes
roofSquareFeetYes
rakesLinearFeetYes
valleysLinearFeetYes
stepFlashingLinearFeetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that by identifying the result as Hover's proprietary *algorithm* output rather than a local formula, and that the value is a percentage. It doesn't disclose auth requirements, whether it counts against an API quota, or whether the factor varies by region/product.

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?

A single well-formed sentence with the verb, the output and its unit, and the input family front-loaded. No filler or repetition of the title.

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?

There is no output schema, yet the description does state the return is a percentage, which covers the main return-value question. However, for a five-parameter computational tool with zero schema description coverage, it leaves the agent guessing about units, valid measurement sources, and the shape of the response.

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

Parameters2/5

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

Schema description coverage is 0% across five required params, so the description must carry the load, and it only groups them generically as 'roof square footage and linear roof measurements'. It never mentions step flashing, rakes, valleys, or hips individually, nor units or expected magnitudes. The parameter names are largely self-describing, which keeps this from a 1.

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?

States a specific verb+resource: computes Hover's algorithmic 'Recommended Roof Waste Factor (%)', which is clearly distinct from the retrieval-oriented siblings (get_estimate, get_job, get_measurements). The purpose is unambiguous. It stops short of a 5 only because it doesn't explicitly contrast itself with the measurement/estimate tools that supply the underlying numbers.

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 guidance on when to use this versus fetching an estimate or measurements, no prerequisites (e.g., must the measurements come from Hover first?), and no exclusions. The only implied usage cue is that all five measurements are the inputs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources