Skip to main content
Glama

OpsRev Roofing AI

Price an EagleView order

eagleview_price_order
Read-only

Check pricing for a measurement report order without placing or purchasing it. Use List EagleView products first for productId and deliveryId.

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_price_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.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the behaviorally important reassurance that nothing is placed or purchased, resolving the main ambiguity an agent would have before invoking a pricing call against an external service. It says nothing about latency, external availability, or whether pricing can change between quote and order.

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 the core action and the non-committal behavior stated first and the prerequisite dependency second. No filler, no restatement of the title.

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?

For a 14-parameter tool with no output schema and no schema descriptions, the definition is far too thin. An agent cannot tell what instructionType should be, what a valid deliveryId/productId pairing looks like, or what shape the returned pricing is in, and must guess on half the required surface.

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?

With 14 parameters, 7 of them required, and 0% schema description coverage, the description names only productId and deliveryId and never explains the opaque required field instructionType, nor changesInLast4Years, buildingId, claimNumber, or poNumber. Two of fourteen parameters annotated is a substantial shortfall against a schema that documents nothing.

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 gives a specific verb and resource: 'check pricing for a measurement report order'. It also distinguishes itself from a purchase flow with 'without placing or purchasing it', which implicitly separates it from eagleview_place_order without naming that sibling.

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

Usage Guidelines4/5

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

It gives explicit ordering guidance: 'Use List EagleView products first for productId and deliveryId', routing the agent to eagleview_list_products before calling this. It lacks any statement of when not to use it (for example, when a price was recently obtained or the order already exists), but the prerequisite is stated clearly.

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