Skip to main content
Glama

OpsRev Roofing AI

Create a JobNimbus contact

jobnimbus_create_contact

Create a new contact in JobNimbus. Confirm the contact details with the user before saving.

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": {
      "firstName": "<firstName>",
      "lastName": "<lastName>"
    },
    "name": "jobnimbus_create_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo
cityNo
emailNo
lastNameYes
firstNameYes
stateTextNo
statusNameNo
mobilePhoneNo
addressLine1No
recordTypeNameNo

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?

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the write/non-idempotent profile is known. The description adds one genuinely useful behavioral rule — require user confirmation before the save occurs — but says nothing about duplicate detection, required-field failures, or what is returned on success.

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 action, and nothing redundant. It is efficient, though the brevity is partly the source of the missing detail rather than a virtue in itself.

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?

A write tool with 10 parameters, no schema descriptions, and no output schema needs far more than two sentences. Key facts an agent must know before calling — how the free-text statusName/recordTypeName fields are meant to be populated, whether duplicates are created, and how the new contact is identified — are all absent.

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?

All 10 parameters have 0% schema description coverage, so the description must carry the burden and does not. It never mentions any field — not the required firstName/lastName, nor the ambiguous ones like recordTypeName, statusName, or stateText — leaving the agent to guess semantics from bare property names and length constraints.

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 contact in JobNimbus"), which is unambiguous on its own. It does not differentiate from the sibling acculynx_create_contact or explain how it relates to jobnimbus_get_contact, so sibling routing is left to the tool name.

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 guidance on when to use this versus the AccuLynx create-contact sibling or when to look up an existing contact first. The only procedural note is "Confirm the contact details with the user before saving," which is a workflow step rather than usage scoping.

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