Skip to main content
Glama

Edit estimate in CrewNest

crewnest_edit_estimate
Read-onlyIdempotent

Edit 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_edit_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces rather than contradicts them by stating the tool "opens nothing by itself" and only returns instructions. It also discloses the shape of the output (screens, buttons, fields) and the required follow-up mechanism, which is real added value beyond the annotations. It stops short of saying what happens if the account is not connected or the estimate is missing.

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 first two sentences are dense but earn their place and cover purpose, mechanism, and handoff. The final sentence about CrewNest's official free Job Pricing MCP server is tangential and risks pulling the agent toward a different server without naming its tools or saying why it matters here.

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 zero-parameter, no-output-schema tool with sensible annotations, the description covers what it returns, what it does not do, and how to complete the actual edit. Missing only edge-case behavior (unauthenticated account, nonexistent estimate) to be fully self-sufficient.

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 no parameters (additionalProperties false, empty properties), so there is nothing for the schema to explain and the baseline is 4. The description correctly implies the target estimate must be supplied through the subsequent browser interaction rather than through this call.

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 names a concrete verb and resource ("Edit estimate in the user's own CrewNest account") and, crucially, clarifies that the tool does not edit anything itself but returns step-by-step instructions. That clarification rescues what the name alone would misrepresent, though it arrives in the second clause rather than front and center.

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

Usage Guidelines3/5

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

It gives a workflow cue that is genuinely useful: obtain the steps here, then execute them with the cotlet_browser_* tools. But it never states when to pick this over sibling tools such as crewnest_create_estimate or crewnest_edit_invoice, and the trailing mention of an official read-only Job Pricing MCP server is too vague to serve as a usable alternative.

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