Skip to main content
Glama

OpsRev Roofing AI

Get EagleView file links

eagleview_get_file_links
Read-only

List all downloadable report file links (PDF, JSON, XML, etc.) 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_file_links"
  }
}

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 the safety profile is covered. The description adds that multiple links may exist and formats vary (PDF, JSON, XML, etc.), but says nothing about link expiry, authentication requirements, or whether an empty result is possible.

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 scope stated immediately and zero filler. Nothing is repeated from the title or schema unnecessarily.

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?

This is a simple single-parameter read tool with annotations covering safety and no output schema to explain. The description conveys what is returned (downloadable file links) and in what variety of formats, which is nearly sufficient; only the shape of the returned link entries is left unstated.

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 burden is on the description, and it does clarify that the single parameter is an EagleView report ID. However, it adds no detail on format beyond what the schema's numeric pattern already enforces, so it only partially compensates for the coverage gap.

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 uses a specific verb ('List') and a specific resource ('downloadable report file links') scoped to an EagleView report ID, so an agent knows exactly what comes back. It does not explicitly contrast with siblings like eagleview_get_report or eagleview_get_report_json, leaving the agent to infer that this returns links rather than report content.

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 when-to-use guidance, no mention of prerequisites (a valid report ID must already exist), and no named alternative for retrieving report content versus report links. Usage is only implied by the phrase 'for an EagleView report ID'.

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