Skip to main content
Glama

OpsRev Roofing AI

Add a JobNimbus note or activity

jobnimbus_add_activity

Post an activity note onto an existing JobNimbus contact or job jnid. Confirm the target record and note 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": {
      "primaryId": "<primaryId>",
      "note": "<note>"
    },
    "name": "jobnimbus_add_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
primaryIdYes
recordTypeNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write profile (readOnly=false, destructive=false, openWorld=true, idempotent=false), so the description's job is to add context — and it does, mandating user confirmation of both target and note text before saving. It omits that the operation is non-idempotent (repeat calls likely create duplicate notes) and does not say what is returned, but the added pre-save confirmation is genuinely useful.

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 sentences, front-loaded with the action and target, followed by the safety instruction. No filler and nothing repeated from the schema or annotations.

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 three-parameter mutation with no output schema, the definition covers the action and the confirmation requirement but leaves real gaps: the accepted values for `recordTypeName`, whether duplicate posts are possible, and what the caller receives back (an activity/note id would matter for follow-up calls).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the load. It maps reasonably onto `note` and `primaryId` (the target jnid) and hints that the record may be a contact or a job, which points at `recordTypeName`. However, it never names `recordTypeName` nor states its accepted values, and that field has no enum in the schema, leaving the agent to guess the discriminator string.

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 verb and resource are concrete: 'Post an activity note' onto 'an existing JobNimbus contact or job jnid,' which separates it from the sibling listing tool (jobnimbus_list_activities) and from create tools for other record types. It stops short of naming an alternative when a user wants a task or file instead, but the intent is unambiguous.

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?

'existing ... contact or job jnid' implies the target record must already exist, and the confirmation instruction gives a workflow step. No when-not guidance or named alternative is provided, so an agent must infer on its own whether a note belongs on a contact versus a job.

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