Skip to main content
Glama

Create estimate in CrewNest

crewnest_create_estimate
Read-onlyIdempotent

Create estimate in the user's own CrewNest account from ChatGPT, Claude or any AI agent. Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser. CrewNest's official API: CrewNest publishes an official, free Job Pricing MCP server with three read-only tools for public price calculations and benchmarks.

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_create_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint=true and destructiveHint=false already declared, the description earns credit for explaining WHY a tool named 'create' is read-only: it returns screens, buttons and fields and 'opens nothing by itself'. That resolves a genuine ambiguity an agent would otherwise have to guess at. It stops short of describing prerequisites such as login state or Cloud Browser availability.

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 core content is front-loaded and useful, but the opening 'Create estimate' framing is misleading until the later clause corrects it. The closing sentence about CrewNest's official free Job Pricing MCP server with three read-only tools is promotional context that does not help an agent select or invoke this tool.

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?

There is no output schema, so the description must describe the return value, and it does: a step-by-step procedure listing screens, buttons and fields, plus the follow-up tools to use. For a zero-parameter planning tool this is close to complete; only auth/session prerequisites are unstated.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is nothing for the schema to document. The description does not explain how the target account or estimate details are conveyed given that no inputs exist, which is a small residual gap.

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 gives a specific verb and resource (create an estimate in the user's own CrewNest account) and immediately clarifies the twist that the tool returns instructions rather than performing the write. It differentiates from the cotlet_browser_* tools that actually execute the steps, though it does not distinguish itself from nearby estimate siblings such as crewnest_edit_estimate or crewnest_configure_estimate_defaults.

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?

It states a clear workflow: this tool returns the step-by-step procedure and 'opens nothing by itself', then the agent should act with the cotlet_browser_* tools. That is an explicit alternative and handoff, but there is no when-not-to-use guidance (e.g. when to skip planning and call a browser action directly).

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