Skip to main content
Glama

OpsRev Roofing AI

Place an EagleView measurement order

eagleview_place_order

Place a billable EagleView measurement report order. Always run Price an EagleView order first and confirm the exact address, product, and cost with the user before ordering.

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": {
      "address": "<address>",
      "city": "<city>",
      "state": "<state>",
      "zip": "<zip>",
      "productId": "<productId>",
      "deliveryId": "<deliveryId>",
      "instructionType": "<instructionType>"
    },
    "name": "eagleview_place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes
cityYes
stateYes
addressYes
countryNo
commentsNo
poNumberNo
productIdYes
buildingIdNo
deliveryIdYes
claimNumberNo
referenceIdNo
instructionTypeYes
changesInLast4YearsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds two details beyond them: the order is billable (it incurs a real cost), and user confirmation is required before committing. It does not say what happens if the same address is ordered twice, even though idempotentHint=false implies a duplicate billable order, which is the main residual gap.

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?

Two short sentences with zero filler, and the critical precondition and safety instruction are front-loaded before the ordering action.

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?

This is a billable, non-idempotent mutation with 14 undocumented parameters and no output schema. The workflow preconditions are well covered, but the description says nothing about which parameters are required and what values they take, or how the order is keyed. That is too thin for a tool of this complexity.

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% across 14 parameters, so the description must carry the full burden. It only gestures at 'address' and 'product'; it never explains productId, deliveryId, instructionType, changesInLast4Years, poNumber, claimNumber, referenceId, or buildingId. An agent effectively has to guess at half the required inputs.

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 states a specific verb and resource: 'Place a billable EagleView measurement report order.' That is clearly distinct from the read/price siblings, and it names the pricing step as its precursor. It stops short of explicitly contrasting itself with eagleview_price_order in the way a 5 would.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit prerequisite ('Always run Price an EagleView order first') and a mandatory confirmation step covering address, product, and cost before ordering. There is no ambiguity about when or how to invoke it.

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