Skip to main content
Glama

OpsRev Roofing AI

Get a Hover inspection

hover_get_inspection
Read-only

Read detailed inspection answers, damage tags, and photo URLs for a Hover inspection 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": {
      "inspectionId": "<inspectionId>"
    },
    "name": "hover_get_inspection"
  }
}

Input Schema

NameRequiredDescriptionDefault
inspectionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 contributes the shape of the payload (answers, damage tags, photo URLs), but says nothing about auth requirements, rate limits, or what happens with an unknown or malformed ID.

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 no filler; the returned fields are enumerated immediately after the verb so an agent can decide relevance at a glance.

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?

For a one-parameter read tool with no output schema, the description is nearly sufficient: it names the returned data categories and the keying identifier. The only real gap is how to obtain a valid inspection ID, which the sibling list tool likely covers elsewhere.

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 parameter, so the description has to carry the meaning. It labels the value as a Hover inspection ID, which is useful, but omits the schema's numeric-only pattern and the 1–90 character bound, leaving format expectations unstated in prose.

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?

Names a specific verb (Read) plus the concrete payload it returns (inspection answers, damage tags, photo URLs) keyed by a Hover inspection ID. That is enough for an agent to distinguish it from list-style siblings, though it never names the counterpart list tool it complements.

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 implied by 'for a Hover inspection ID' – call it when you already hold an ID and need the detail. There is no explicit when-not guidance or pointer to hover_list_inspections for discovering IDs, so the agent must infer the routing.

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