JobNimbus MCP Server

by drummouse

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

jn_list_tasks

List tasks in JobNimbus, filter by related contact or job jnid, and specify number of tasks to retrieve.

Instructions

List tasks 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_list_tasks"
  }
}

Input Schema

Name	Required	Description
`from`	No
`size`	No
`related_jnid`	No	Filter by related contact or job jnid

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 9, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavior. It only states a basic list operation, omitting details about pagination (via 'from' and 'size'), filtering (via 'related_jnid'), or whether the operation is read-only (inferred but not stated).

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

Conciseness3/5

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

The description is a single sentence, which is concise. However, it lacks detail that would add value; a slightly longer description including parameter behavior would be more effective without sacrificing conciseness.

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?

Given the absence of annotations or output schema, and three parameters, the description is insufficient. It does not explain pagination behavior, response structure, or the optional filtering parameter, leaving the agent with minimal context for correct invocation.

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

Parameters1/5

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

Schema coverage is only 33%, as only 'related_jnid' has a description in the schema. The tool description does not explain the parameters 'from' and 'size' or their role in pagination, leaving the agent without crucial context about filtering and pagination.

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 'List tasks in JobNimbus' clearly states the action (list) and resource (tasks), making the tool's purpose immediately understandable. It is not a tautology and distinguishes from sibling tools that list other entities.

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 versus alternatives like jn_list_activities or jn_list_notes. There is no mention of prerequisites, filter limitations, or contexts where this tool is appropriate.

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