Skip to main content
Glama

OpsRev Roofing AI

List Hover jobs

hover_list_jobs
Read-only

List or search Hover jobs in the organization. Pass search (3+ characters) to match job name, address, or user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hover_list_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
perNo
pageNo
searchNo
sortByNo
archivedNo
sortOrderNo

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 and the bar is lowered. The description adds the organizational scoping constraint but says nothing about pagination behavior, total counts, default sort, or whether archived jobs are included by default — the `archived` parameter's default behavior is a meaningful open question it leaves unaddressed.

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 sentences, zero waste, with the core list operation front-loaded ahead of the search modifier. Nothing is redundant with the title or annotations.

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?

Six optional parameters including pagination and an archived filter, but the description doesn't mention pagination, sort defaults, or archived inclusion (there is no output schema, so return shape is exempt). Adequate but leaves filter semantics entirely to inference.

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%, so the description carries the full burden, yet it explains only one of six parameters. The `search` explanation is genuinely additive (it names the matched fields — name, address, user — which the schema does not), but `per`, `page`, `sortBy`, `sortOrder`, and especially `archived` are left entirely undefined for the agent.

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?

States a specific verb pair (list/search) and resource (Hover jobs) plus scope (in the organization), which separates it from hover_get_job and from the AccuLynx/JobNimbus/Leap list_jobs siblings via the provider qualifier. It does not explicitly state how it differs from provider-adjacent listers like hover_list_estimates, but the resource is unambiguous.

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?

The sentence about passing search when you want to match name, address, or user implies the search-vs-enumerate usage pattern, but there is no explicit when-to-use/when-not guidance relative to hover_get_job (single record) or the other hover_list_* tools. The agent must infer the routing decision.

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