Skip to main content
Glama

OpsRev Roofing AI

Add a Hover job note

hover_add_note

Create a note on a Hover job. Requires the email of a Hover user with access to the job. Confirm with the user before saving.

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>",
      "body": "<body>",
      "currentUserEmail": "<currentUserEmail>"
    },
    "name": "hover_add_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
jobIdYes
currentUserEmailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With annotations already declaring readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, the description usefully adds the authorization requirement and a human-confirmation step that no annotation conveys. It does not warn about the non-idempotent risk of duplicate notes on retry, nor mention visibility, limits, or what the call returns, so the added context is partial.

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?

Three short sentences, purpose first, then prerequisite, then the confirmation safeguard. Nothing is redundant or buried, and every sentence contributes an actionable fact.

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 simple three-parameter write tool with safety annotations present, the description covers purpose, authorization and confirmation, which is close to sufficient. However, there is no output schema and the description never indicates what comes back after the note is created, and the body content expectations are left entirely implicit.

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 and only partly delivers: it explains currentUserEmail as the email of a Hover user with job access, but says nothing about jobId (must be a valid existing job) or body (1-2000 characters, note content). Two of three parameters remain semantically bare.

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 first sentence states a specific verb and resource ("Create a note on a Hover job"), which is enough to distinguish it from the read counterparts like hover_list_notes and hover_get_job. It stops short of explicitly contrasting itself with other write tools, but the platform-qualified name plus a clear action verb leave no ambiguity about what it does.

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?

The description gives a concrete precondition (the caller must supply the email of a Hover user with access to the job) and an operational rule (confirm with the user before saving), which is real guidance an agent needs before invoking a write. It does not name alternatives or state when not to use it, so it falls short of a 5.

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