CrewNest MCP Server

crewnest_guide

Start here to learn how to work in CrewNest: prepare estimates, manage jobs, assign crew, and find the screens and sign-in link.

Instructions

How to work in CrewNest (prepare estimates and manage jobs and crew assignments): its screens and the sign-in link. Call this first.

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": "crewnest_guide"
  }
}

Input Schema

Name	Required	Description	Default
`task`	No	What you want done in CrewNest, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the burden of behavioral disclosure. It implies this is a safe informational guide and says it covers screens and a sign-in link, but it does not describe the response shape, whether it is read-only, or whether any authentication or state change is involved.

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

Conciseness4/5

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

The definition is short and front-loads the tool's purpose, followed by the key 'Call this first' instruction. The parenthetical is slightly dense but every part contributes to understanding the tool's role.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity guide tool with one optional parameter and no output schema, the description gives enough context to select and invoke it: what it covers and when to call it. It could be stronger by clarifying whether the guide is static or tailored by the task parameter, but it is broadly complete.

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?

There is one optional parameter, and schema coverage is 100%, so the schema already explains that 'task' means what the user wants done in CrewNest. The description adds no further detail about how to phrase the task or how it influences the guide returned, so the baseline applies.

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 identifies this as an orientation/guide tool for CrewNest, covering screens, estimates, jobs, crew assignments, and the sign-in link. It is clearly distinct from the sibling UI-action tools such as crewnest_click and crewnest_read, though the opening phrase 'How to work' is less precise than a direct verb-resource statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The instruction 'Call this first' gives explicit sequencing guidance for an agent entering CrewNest. It does not name alternatives or explain when not to call it, but the onboarding role makes the intended usage clear.

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

Deploy Server