Skip to main content
Glama

OpsRev Roofing AI

List Leap CRM job notes

leap_list_job_notes
Read-only

Read notes attached to a Leap CRM 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": "leap_list_job_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered by structured data. The phrase "attached to a Leap CRM job" adds the scoping constraint, but the description never mentions pagination, ordering, volume limits, or whether an empty list is normal – gaps that matter for an open-world listing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or repetition, which is structurally clean. It is however so terse that the available space is not used to convey scope or return behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 the shape is simple, but with no output schema and 0% parameter coverage the description should state what a note contains and whether results are paginated or capped. None of that is present, leaving the agent guessing at the response shape.

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%: jobId carries only type, pattern and length constraints, with no prose explaining what it identifies. The description never mentions the jobId parameter, so it does not compensate for the coverage gap; only the bare implication that a job-scoped read needs a job id can be inferred.

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 has a specific verb ("Read") plus resource ("notes attached to a Leap CRM job"), which clearly separates it from the write-side sibling leap_add_job_note. It never names a sibling or states how it differs from other Leap read tools, so it stops short of full differentiation.

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?

There is no when-to-use or when-not-to-use guidance, and no alternatives are named; the sibling leap_add_job_note (for writing notes) is never mentioned as a complement. A caller must infer the usage from the verb alone.

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