Skip to main content
Glama

OpsRev Roofing AI

Get Hover model measurements

hover_get_model_measurements
Read-only

Fetch structured JSON roof and exterior measurements for a Hover model ID. Defaults to summarized_json.

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": {
      "modelId": "<modelId>"
    },
    "name": "hover_get_model_measurements"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelIdYes
versionNo

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 that output is structured JSON and that summarized_json is the default, but says nothing about what the other versions return, whether the model must exist or be processed, or any latency/quota behavior for an open-world external fetch.

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?

Two tight sentences, front-loaded with the action and resource, and the default is placed last where it belongs. Nothing is redundant, though the terseness leaves gaps that conciseness alone cannot excuse.

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

Completeness2/5

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

With no output schema and 0% parameter description coverage, the description is the only place semantics could live, and it leaves the five version modes opaque. For a tool whose entire value is choosing the right measurement payload, that is a substantive omission.

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%, so the description must carry the load. It clarifies modelId as a Hover model ID (numeric pattern only visible in schema) and notes the default for version, but the five enum values (full_json, roof_lines, sketch_json, paint_measurements) are entirely unexplained — the agent cannot tell what payload each yields.

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 names a specific verb and resource ('Fetch structured JSON roof and exterior measurements') and scopes it to a 'Hover model ID', which separates it from vendor siblings such as eagleview_get_measurements. It stops short of explicitly contrasting the two measurement providers, so a 4 rather than a 5.

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?

It states the default version ('Defaults to summarized_json'), which implicitly tells the agent the common call needs no version argument. However, there is no guidance on when to pick any other version, and no mention of alternatives like eagleview_get_measurements or how to discover a modelId.

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