Skip to main content
Glama

OpsRev Roofing AI

Add a Leap CRM job note

leap_add_job_note

Add a note to an existing Leap CRM job. Confirm the job and exact note 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>",
      "note": "<note>"
    },
    "name": "leap_add_job_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
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 the mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false). The description adds real value beyond them by requiring the agent to confirm the job and exact note text with the user before saving. It does not warn that non-idempotent repeated calls will create duplicate notes, nor whether the note is appended versus replaces anything, which leaves meaningful gaps for a write tool.

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, both earning their place: the first defines the operation, the second front-loads the confirmation safeguard. Nothing is redundant or buried.

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 two-parameter mutation with no output schema, the description covers the core action and the confirmation step. It omits what the call returns (e.g., a created note identifier) and duplicate-note behavior on retry, which an agent needs for a non-idempotent write.

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 of explaining the two parameters. It only implies the concepts ('the job', 'the exact note') and adds that the job must already exist; it never addresses the numeric-string jobId format, the 1-2000 character note bound, or whether the note is plain text or markup.

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 states a specific verb and resource: 'Add a note to an existing Leap CRM job.' That distinguishes it from the read-oriented sibling leap_list_job_notes and from note tools on other CRMs. It stops short of explicitly naming a sibling or clarifying scope boundaries, so a 4 rather than a 5.

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?

'Add a note to an existing Leap CRM job' implies when the tool applies, and the confirmation instruction establishes a pre-save workflow. However, there is no guidance on when to prefer this over alternatives such as leap_create_task for actionable follow-ups, or when a note is inappropriate. Usage is implied rather than stated.

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