Skip to main content
Glama

Configure estimate defaults in CrewNest

crewnest_configure_estimate_defaults
Read-onlyIdempotent

Configure estimate defaults 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_configure_estimate_defaults"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the safety profile is known. The description reinforces this with 'opens nothing by itself' and adds genuinely new information about the return value (step-by-step screens, buttons and fields) and the required follow-up tool family. It stops short of describing whether the instructions depend on account state or plan tier, which would matter for a guided-setup tool.

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 two clauses are front-loaded and efficient, and the 'then do it with the cotlet_browser_* tools' instruction is correctly placed right after the caveat. The final sentence about CrewNest's official free Job Pricing MCP server and its three read-only tools is unrelated to invoking this tool and reads as promotional filler that dilutes the actionable content.

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 guidance tool with no output schema, the description supplies what an agent needs: what is returned (a step-by-step procedure), that nothing is mutated, and which tools to use to actually apply it. Prerequisites such as being signed in to the user's CrewNest account are only implied by 'the user's own CrewNest account'.

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 nothing for the description to disambiguate and the baseline of 4 applies. The 100% schema coverage is trivially satisfied by an empty object.

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 uses a specific verb and resource ('Configure estimate defaults in the user's own CrewNest account') and immediately clarifies the real behavior: it returns step-by-step instructions rather than performing the change. That distinction from the sibling configure_* and estimate-mutation tools (create_estimate, edit_estimate, send_estimate) is inferable from the name plus this clarification, though no sibling is named explicitly.

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 gives a clear usage path: call this to get the procedure, then execute it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser. It also states a negative condition ('opens nothing by itself'), which prevents the agent from assuming the change happened. It does not discuss how to choose between this and other configuration tools, but the resource-level naming makes that decision straightforward.

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