JobNimbus MCP Server

Overview Schema Source Related Servers Discussions Admin

jn_list_estimates

Retrieve a list of estimates from your JobNimbus account, with optional filtering by related entity ID and pagination controls.

Instructions

List estimates 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_estimates"
  }
}

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.4/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not explain pagination defaults, whether results are sorted, or any side effects. It only states the action without context.

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 extremely concise at one sentence, but it sacrifices necessary information. It is not structured to highlight key details; it reads as a minimal placeholder rather than a well-edited summary.

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 tool has multiple parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain pagination, filtering options, or return format, making it insufficient for proper agent usage.

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%, meaning parameters like 'from', 'size', and 'related_jnid' are not described in the schema. The description adds no explanation of these parameters, leaving their purpose entirely implicit.

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 clearly states the action (list) and resource (estimates) in JobNimbus. However, it does not differentiate from sibling list tools like jn_list_jobs or jn_list_contacts, lacking specificity on scope or filtering.

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. No mention of prerequisites, filtering criteria, or pagination behavior. The description is solely a statement of function.

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