Skip to main content
Glama

OpsRev Roofing AI

Get EagleView report JSON

eagleview_get_report_json
Read-only

Fetch the structured EV JSON measurement file (fileType 107) 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_report_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 the returned artifact is a specific file type (107), which is useful because no output schema exists, but it omits failure modes, availability/prerequisite behavior, and whether the file is generated on demand.

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 front-loaded sentence with the return artifact and the scoping identifier in the first clause. No filler, no redundancy, nothing that could be cut.

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?

With no output schema, the description's brief characterization of the return value (structured EV JSON measurement file, fileType 107) is genuinely needed and present. However, for a network-bound open-world read with an undocumented parameter, it leaves out prerequisite state and how it differs from the sibling retrieval tools.

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% for the single parameter, so the description must carry the burden, yet it only restates that reportId is an EagleView report ID — essentially echoing the property name. It adds no format detail (the schema's numeric pattern), no length constraints, and no hint about where to obtain a valid ID.

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 ("Fetch") and a precise resource ("structured EV JSON measurement file (fileType 107)") scoped to an EagleView report ID, and the fileType constant makes the artifact concrete. It stops short of naming which sibling to prefer (e.g. eagleview_get_report or eagleview_get_measurements), so an agent must infer the distinction from the file-type detail alone.

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: fetch this when you need the machine-readable JSON measurement file rather than some other EagleView artifact. There is no explicit when-to-use, when-not-to-use, or named alternative, and no mention of prerequisites such as the report needing to exist or be processed first.

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