Skip to main content
Glama

OpsRev Roofing AI

Get Leap CRM job workflow history

leap_get_job_workflow_history
Read-only

Read stage transition history for 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_get_job_workflow_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without description help. The description adds that the read is specifically of stage transitions, which sharpens what comes back. It does not disclose ordering, truncation, or whether history is complete for older jobs — meaningful gaps for a history endpoint, but tolerable given the annotations.

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?

One short sentence, front-loaded with the verb and resource, with no filler. It is efficient, though the terseness leaves little room for the usage and scope detail an agent would benefit from.

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 no output schema, the description covers the essentials of what is read and for which entity. What is missing is return-shape context — whether entries include timestamps, actor, from/to stages, and whether results are bounded. An agent can call it correctly but cannot predict the response.

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%, so the description must carry the burden for the single jobId parameter. Saying "Leap CRM job" does disambiguate that the id belongs to Leap rather than the AccuLynx or JobNimbus siblings, which is real added meaning. It still says nothing about the id's format or where to obtain it, leaving the digit-pattern constraint to the schema alone.

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 gives a specific verb and resource: "Read stage transition history for a Leap CRM job." That is clearly narrower than leaping to the whole job record via leap_get_job, so an agent can distinguish it. It stops short of naming a sibling or stating scope limits (time range, pagination), which keeps it below 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must infer that this is the tool for auditing pipeline movement rather than fetching job details. A single clause such as "use leap_get_job for current status" would have closed the gap.

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