JobNimbus MCP Server

by drummouse

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

jn_create_contact

Create a new contact in JobNimbus by specifying name, email, phone, address, status, tags, and custom fields.

Instructions

Create a new contact in JobNimbus.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jn_create_contact"
  }
}

Input Schema

Name	Required	Description
`zip`	No
`city`	No
`tags`	No
`email`	No
`phone`	No
`country`	No
`last_name`	No
`first_name`	No
`state_text`	No
`status_name`	No
`display_name`	No
`mobile_phone`	No
`address_line1`	No
`custom_fields_json`	No	JSON string of custom field key-value pairs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 9, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description must disclose behaviors. It only states 'create' but omits details like authentication requirements, idempotency, or what happens on duplicate creation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (7 words) but lacks structured information. It fails to earn its place by omitting critical details needed for selection and invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 14 parameters, no required fields, no output schema, and no annotations, the description is severely incomplete. It does not help an agent understand valid inputs or expected outcomes.

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 coverage is only 7% (only custom_fields_json has a description). The tool description adds no parameter explanations, leaving the agent without guidance for 14 fields.

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 clearly states the action ('Create') and resource ('new contact in JobNimbus'), distinguishing it from sibling tools like jn_update_contact (update) and jn_get_contact (get).

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?

No guidance on when to use this tool vs alternatives, such as when creating a contact vs updating an existing one. No prerequisites or usage context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.