Skip to main content
Glama

Send estimate in CrewNest

crewnest_send_estimate
Read-onlyIdempotent

Send 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_send_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and non-destructive behavior, so the safety profile is covered. The description usefully adds that nothing is opened and that the return is a screen-by-screen recipe for the user's own account, but it omits details such as whether the steps are account-specific, what happens on repeated calls, or limits on freshness. With annotations carrying most of the load, this lands at a mid score.

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 behavior is front-loaded in the first two sentences, but the final sentence about CrewNest's separate official Job Pricing MCP server is promotional and does not help the agent call this tool or choose between alternatives. Removing it would sharpen the definition.

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?

With no input parameters and no output schema, the description does most of the work by explaining what comes back (step-by-step screens, buttons, fields) and that no action is taken. It is nearly complete, though a note on what to do if the user has no Cloud Browser session would close the gap.

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 there is no parameter semantics for the description to explain; the baseline for a no-parameter tool applies. Nothing in the description misleads about inputs.

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?

Names a specific resource (estimate) and, crucially, clarifies the misleading verb by stating it "Returns how to do it in CrewNest step by step... and opens nothing by itself." An agent can tell this is an advisory tool rather than an executing one, although the description never contrasts it with siblings like crewnest_create_estimate or crewnest_edit_estimate.

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?

Provides a workflow: call this to get the steps, then perform them with the cotlet_browser_* tools in the Cloud Browser, which is real usage context. However, there are no exclusions and no routing against the many sibling estimate tools (create/edit/remind), so the agent must infer when this is the right entry point.

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