Skip to main content
Glama

OpsRev Roofing AI

Get EagleView waste measurements

eagleview_get_measurements
Read-only

Read structure waste factor tables and roof area measurements for an EagleView report 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": {
      "reportId": "<reportId>"
    },
    "name": "eagleview_get_measurements"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 safety is covered. The description adds that this is a read of waste factor tables plus roof area measurements, but says nothing about prerequisites (must the report be processed/ready?), behavior on an unknown or not-yet-complete report ID, or units/rounding of the measurements.

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?

A single front-loaded sentence with no filler or redundant restatement of the title. It is efficient, though the brevity edges toward under-specification rather than crispness.

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?

For a one-parameter, read-only measurement tool with no output schema, the description covers the essentials of what is returned at a high level. It omits prerequisite report state, error behavior, and any hint about the shape of the measurement data, which an agent would need to use results confidently.

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%, so the only meaning the description supplies is that the lone parameter is an EagleView report ID — which the name 'reportId' largely conveys already. The numeric-only pattern, length bounds, and where to source a valid ID are left to the schema or unstated.

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 ('Read') and concrete resources ('structure waste factor tables and roof area measurements'), scoped to an EagleView report ID. It is clearly distinguishable from report-listing or file-link siblings. It stops short of explicitly contrasting itself with eagleview_get_report_json, which likely also returns measurement data.

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: 'for an EagleView report ID' tells the agent it needs a report identifier, presumably obtained from eagleview_list_reports or eagleview_get_report. There is no explicit when-to-use, when-not-to-use, or named alternative vs. the Hover measurement siblings or the EagleView report/JSON tools.

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