Skip to main content
Glama

OpsRev Roofing AI

Create an AccuLynx job

acculynx_create_job

Create a new unassigned lead linked to an existing primary contact. Confirm the contact and job 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": {
      "contactId": "<contactId>"
    },
    "name": "acculynx_create_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
priorityNo
contactIdYes
locationAddressNo

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?

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety and mutation profile is covered structurally. The description adds real value by specifying the created entity is an 'unassigned lead' tied to an existing contact and by imposing a user-confirmation step. It does not disclose what is returned on success or whether duplicate leads are possible.

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?

Two short sentences, front-loaded with the creation semantics and followed by the confirmation constraint — no filler. It is tightly written, though the second sentence is a procedural directive rather than definitional content.

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 four-parameter create tool with a nested address object and no output schema, the description covers the intent and the confirmation requirement but leaves parameter meaning and the post-creation result undocumented. Adequate to know what the tool does, insufficient to call it confidently without reading the schema closely.

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% across four parameters, one of which is a nested address object with five required fields. The description only obliquely references 'contact and job details' and never explains contactId format, the priority enum values, the notes length limit, or the structure of locationAddress. With zero schema-level documentation, the description should be compensating but is not.

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 ('Create a new unassigned lead') plus a key precondition ('linked to an existing primary contact'), which tells an agent this is a job/lead creation requiring a pre-existing contact. It does not explicitly contrast with siblings like jobnimbus_create_job or acculynx_create_contact, so it stops short of full sibling differentiation.

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?

There is a clear procedural instruction to confirm contact and job details with the user before creating, which is actionable guidance for a mutating tool. However, it offers no guidance on when to choose this over alternatives, nor on what to do if the contact does not exist (e.g., call acculynx_create_contact first).

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