Skip to main content
Glama
Sign In
JobNimbus MCP Server

JobNimbus MCP Server

by drummouse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

jn_create_note

Attach a note to a specific contact or job in JobNimbus by providing the note content and the related record's ID.

Instructions

Add a note to a contact or job in JobNimbus.

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": {
      "note": "<note>",
      "related_jnid": "<related_jnid>",
      "related_type": "<related_type>"
    },
    "name": "jn_create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesNote text content
related_jnidYesjnid of the contact or job
related_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states 'Add a note' without mentioning permissions, side effects, return values, or any constraints, leaving the agent uninformed about essential behavior.

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 description is a single sentence, highly concise, and front-loaded with the action verb 'Add'. Every word is necessary with no redundancy.

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?

The description is minimally viable: it states the core function and the allowed target types. However, it lacks details on success outcomes, error handling, or how to obtain the required jnid, leaving gaps for a tool with three required parameters and no output schema.

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?

The description does not add meaning beyond the input schema. It reiterates that the note relates to a contact or job but provides no additional context about parameter formats, validation, or usage patterns. Schema coverage is 67%, but the description fails to compensate.

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 'Add a note to a contact or job in JobNimbus.', specifying the verb (Add), resource (note), and target (contact/job). This distinguishes it from sibling create tools like jn_create_contact and jn_create_job.

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 is provided on when to use this tool over alternatives, such as jn_create_task or jn_list_notes. The description does not mention prerequisites or contextual clues for selection.

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

Deploy Server

Other Tools