Skip to main content
Glama

List estimates in CrewNest

crewnest_list_estimates
Read-onlyIdempotent

List estimates 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_list_estimates"
  }
}

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so safety is covered; the description earns credit for the non-obvious disclosure that it performs no account action and returns instructions instead. It also names the specific output shape ("screens, buttons, fields"), which the annotations cannot convey. The final sentence about a separate official MCP server adds promotional context rather than behavioral detail about this 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 purpose and the no-side-effect handoff are front-loaded, which is good. But the second sentence is overloaded (output format, side-effect disclaimer, and execution channel in one breath), and the closing sentence about CrewNest's official Job Pricing MCP server is tangential to invoking this tool and reads as filler.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does: a step-by-step click path plus the handoff to cotlet_browser_* tools. An agent knows enough to call it and knows what to do next. The unrelated API mention is the main completeness defect, since it implies an alternative that is never qualified.

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 input schema is an empty object with additionalProperties=false, so there are no parameters whose meaning needs explaining; the 0-param baseline applies. The description correctly implies no arguments are needed but does not explicitly state that the call is argument-free or scoped implicitly to the authenticated user.

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?

Opens with a specific verb+resource ("List estimates in the user's own CrewNest account") and immediately reclassifies itself as a guidance tool that "returns how to do it in CrewNest step by step" rather than raw data. That distinction separates it from siblings like crewnest_create_estimate or crewnest_edit_estimate. The trailing sentence about CrewNest's official Job Pricing MCP server is a non-sequitur that blurs the stated purpose without adding a usable distinction.

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?

Explicitly states the workflow: call this first to get the click path, then execute with cotlet_browser_* tools in the Cloud Browser, and notes the tool "opens nothing by itself." That is clear context for invocation. It never states when NOT to use it or which sibling to pick for an alternative listing path, and the official-API sentence dangles without saying under what conditions an agent should prefer it.

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