Skip to main content
Glama

OpsRev Roofing AI

Get a Hover estimate

hover_get_estimate
Read-only

Read detailed material takeoff line items, quantities, waste factors, and totals for a Hover estimate/production list ID.

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": {
      "estimateId": "<estimateId>"
    },
    "name": "hover_get_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
estimateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 real value by enumerating what the response contains (line items, quantities, waste factors, totals), which matters because no output schema exists. It stops short of stating error behavior for an unknown ID or any access/prerequisite requirements.

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?

One sentence, verb-first, with no filler or restatement of the title. The noun list is dense but each item carries content the agent needs to know about the payload.

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 a single-parameter read with rich annotations and no output schema, the description covers the resource and the shape of the return data adequately. What remains unstated is how to source the ID and what happens on a bad or inaccessible ID — minor for a read tool.

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 0% for the single estimateId parameter, so the schema supplies only a numeric pattern and length bounds. The description contributes that the identifier may be a Hover estimate ID or a production list ID, which is meaning beyond the schema, but it does not explain where to obtain the ID or what format it takes.

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 (read) and a specific resource (material takeoff line items, quantities, waste factors, totals) scoped to a Hover estimate/production list ID. An agent can distinguish it from hover_get_inspection or hover_get_model_measurements, though the description never names those siblings to sharpen the boundary.

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?

Usage is only implied: the phrase 'for a Hover estimate/production list ID' signals that an ID is the entry point, presumably from a list tool. There is no explicit when-to-use, when-not-to-use, or alternative named, so an agent must infer whether this or hover_get_model_measurements answers its question.

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