JobNimbus MCP Server

by drummouse

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

jn_list_work_orders

Retrieve work orders from JobNimbus. Filter by related job ID and paginate results with size and offset parameters.

Instructions

List work orders 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_work_orders"
  }
}

Input Schema

Name	Required	Description	Default
`from`	No
`size`	No
`related_jnid`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 9, 2026

TDQS

C2.3/5.0

Behavior1/5

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

With no annotations, the description must cover behavioral traits. It only states 'list work orders' and provides no information on side effects, authentication needs, pagination behavior, or ordering. Completely insufficient.

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?

While the description is very short, it is under-specified rather than concise. It fails to include crucial information, so the minimal length is a deficit, not a virtue.

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 3 undocumented parameters, no output schema, and numerous sibling tools, the description is far from complete. It lacks explanatory context for parameters, return data, and usage boundaries.

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 description coverage is 0%, yet the description adds no meaning to parameters (from, size, related_jnid). Users get no indication of parameter purpose or valid values.

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 states 'List work orders in JobNimbus,' which clearly identifies the verb (list) and resource (work orders). It distinguishes itself from sibling tools that list different entities (jobs, contacts, etc.).

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 versus alternatives like list_jobs or list_tasks. No context for prerequisites or typical scenarios.

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