Skip to main content
Glama

OpsRev Roofing AI

Get a Leap CRM job

leap_get_job
Read-only

Read one job by its Leap CRM job ID, including address, customer, trades, and financial details.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations cover the primary behavioral traits (readOnlyHint, destructiveHint), which reduces the description's burden. The description adds contextual behavioral data by specifying the depth of the returned data, making it moderately transparent.

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?

The definition is a single, efficient sentence. It front-loads the action and the specific identifier, and the listing of included details is concise without being redundant.

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?

Given the tool only has one input, the description is quite complete. It clearly defines the input mechanism and enumerates the specific data domains the output will cover, which is sufficient for a lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since schema description coverage is 0%, the description is essential for providing meaning. It clarifies that 'jobId' refers specifically to the 'Leap CRM job ID,' grounding the abstract parameter name in a specific external system context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the action ('Read'), the resource ('one job'), and the identifier used ('Leap CRM job ID'). It also lists the content scope (address, customer, trades, financial details), providing a clear picture of the function.

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 phrasing 'Read one job' clearly implies this is for singular retrieval, helping the agent distinguish it from a potential 'list' tool. However, it does not explicitly contrast the usage against other retrieval methods within the sibling tools context.

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