Skip to main content
Glama

OpsRev Roofing AI

List Hover job estimates

hover_list_estimates
Read-only

List estimate and material list IDs (productionListIds) generated for a Hover job.

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": {
      "jobId": "<jobId>"
    },
    "name": "hover_list_estimates"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

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 safety is covered. The description adds real context by specifying that only IDs are returned rather than full estimate details, but it says nothing about result ordering, empty-result behavior for jobs with no estimates, or pagination.

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?

One sentence, front-loaded with the verb and resource, and the clarifying parenthetical is placed immediately after the noun it disambiguates. There is no filler.

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?

For a one-parameter read tool with annotations covering the safety profile, this is close to adequate, but the description leaves the caller unsure how jobId maps to Hover's ID space and how this list relates to hover_get_estimate. No output schema exists, so the ID-only return shape is the one thing the description does usefully cover.

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% and the single jobId parameter has a pattern, length bounds, and required flag but no textual meaning. The description implies the jobId is a Hover job identifier by saying 'generated for a Hover job', which slightly compensates, but it does not say whether the ID is a Hover-internal ID or an external job reference.

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?

A specific verb (List) plus the exact resource (estimate and material list IDs, clarified as productionListIds) generated for a Hover job. The parenthetical alias is genuinely useful because it disambiguates the ID type from other estimate identifiers, though it does not explicitly distinguish itself from hover_get_estimate.

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?

No statement of when to use this vs hover_get_estimate or hover_get_job. The workflow (list IDs first, then fetch details) is only inferable from the word 'IDs'; there are no exclusions, prerequisites, or named alternatives.

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