Skip to main content
Glama

OpsRev Roofing AI

Create a JobNimbus task

jobnimbus_create_task

Create a task or appointment in JobNimbus, optionally linked to a job or contact jnid. Confirm the task 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": {
      "title": "<title>"
    },
    "name": "jobnimbus_create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
dateEndNo
dateStartNo
relatedIdNo
descriptionNo
recordTypeNameNo

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, openWorldHint=true, idempotentHint=false and destructiveHint=false, so safety is covered structurally. The description adds the useful 'confirm before saving' human-in-the-loop rule, but it omits consequences an agent would care about: idempotentHint=false means retries can create duplicates, and the description says nothing about that or about what a created record returns.

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, front-loaded with the action and then the constraint, with no padding or restatement of the title. Every clause carries information.

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?

For a six-parameter, zero-coverage mutation tool with no output schema, the definition is under-specified: the meaning and format of the date fields, what recordTypeName controls (task vs appointment, presumably), and the shape of the response are all absent. What is present is correct but too thin relative to the tool's complexity.

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 six parameters, so the description carries the full burden, and it only clarifies relatedId ('a job or contact jnid'). The two integer constraints dateStart and dateEnd are left completely unexplained - no units, format, or whether they are epoch milliseconds - and recordTypeName and description get no mention at all.

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?

States a specific verb and resource ('Create a task or appointment in JobNimbus') and immediately scopes it as optionally linked to a job or contact jnid, which separates it from list/get siblings. It does not explicitly name a sibling it is not, so it stops short of a 5.

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 a workflow directive ('Confirm the task details with the user before saving'), which is useful procedural guidance. However, it never says when to use this versus, say, jobnimbus_add_activity or a note-adding tool, and no prerequisites (permissions, required IDs) are stated.

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