Skip to main content
Glama

OpsRev Roofing AI

Create a Leap CRM task

leap_create_task

Create a task in Leap CRM assigned to a role group (customer_rep, estimators, subs, or company_crew). Confirm details with the user before creating.

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": {
      "title": "<title>",
      "assignTo": "<assignTo>"
    },
    "name": "leap_create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdNo
notesNo
titleYes
dueDateNo
assignToYes
isHighPriorityNo

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?

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds a genuine behavioral rule (confirm with the user before creating) but does not disclose permission requirements or what happens when jobId is omitted from a task creation.

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 short sentences with no filler; the purpose is front-loaded and the confirmation rule follows immediately. Nothing is wasted 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 six-parameter mutation tool with no output schema, the definition covers purpose and the role-group assignment concept but leaves the jobId linkage and field semantics undocumented. It is adequate for an agent that reads the schema, but it is not complete on its own.

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 it only restates the assignTo enum values, which the schema already lists. It says nothing about jobId linking the task to a job, the dueDate format, what notes or isHighPriority do, or title constraints, so most of the six parameters remain unexplained.

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 uses a specific verb and resource ('Create a task in Leap CRM') and names the target system, which separates it from the jobnimbus_* and acculynx_* create tools. It also names the assignment dimension (role groups), so an agent knows the scope of the operation, though it does not explicitly route against siblings like leap_add_job_note.

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 description gives one procedural guideline: confirm details with the user before creating. It does not say when this tool should be chosen over related tools (such as adding a note to a job) or any preconditions like needing an existing jobId. Usage is implied rather than spelled out.

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