Skip to main content
Glama

OpsRev Roofing AI

Get an EagleView report

eagleview_get_report
Read-only

Read full report details including status, property address, roof measurements, and pitch table by 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_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 value by disclosing what the response contains (status, address, measurements, pitch table), but says nothing about external-call latency, rate limits, or failure behavior that openWorldHint implies.

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?

One front-loaded sentence with no filler; the resource and keying parameter come first and the returned fields follow. It is appropriately sized for a simple getter, with only the enumerated field list costing a little length.

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 with no output schema and no parameter documentation, the description is adequate: it covers both the input key and the shape of the returned data. It falls short on sibling differentiation and on where the required reportId comes from, which an agent still has to infer.

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 reportId parameter, and the schema only supplies a numeric pattern and length bounds. The description partially compensates by stating the ID identifies the EagleView report whose details are read, but it adds no format or sourcing guidance beyond that.

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 resource (full report details), then enumerates the returned content: status, property address, roof measurements, and pitch table, keyed by report ID. This makes the tool's job clear, though it never distinguishes itself from the near-identically named sibling eagleview_get_report_json.

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?

There is no explicit when-to-use or when-not-to-use guidance. The phrase 'by report ID' only implies that a report identifier must already exist (presumably from eagleview_list_reports), and nothing explains when to pick this over eagleview_get_report_json, eagleview_get_measurements, or eagleview_get_file_links.

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