Skip to main content
Glama

Get estimate conversion report in CrewNest

crewnest_get_estimate_conversion_report
Read-onlyIdempotent

Get estimate conversion report 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_get_estimate_conversion_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Adds meaningful behavior beyond the annotations: it returns instructions and opens nothing by itself, so the agent must use browser tools to act. Annotations already cover read-only and idempotent safety, but the description adds the crucial non-execution and next-step behavior.

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?

Core behavior is in the second sentence, but the first includes generic 'from ChatGPT, Claude or any AI agent' phrasing and the third sentence about an official Job Pricing API is unrelated to invoking this tool. It is not excessively long, but the unrelated sentence does not earn its place.

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 read-only tool with no output schema, the description explains the key return: step-by-step instructions with screens/buttons/fields, and that execution requires browser tools. It still does not explain what the estimate conversion report contains or how it relates to sibling report tools, so it is not fully complete.

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?

There are no input parameters, so the baseline is 4. The description does not need to elaborate parameter meaning and does not introduce parameter constraints.

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 identifies the resource (estimate conversion report) and what the tool actually returns: step-by-step CrewNest instructions with screens, buttons, and fields, not the report itself. It does not explicitly distinguish this from sibling report tools, and the opening 'Get ... report' wording initially suggests data retrieval, so it is not a 5.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not guidance versus sibling report tools or the CrewNest UI. It only states a procedural follow-up path: use cotlet_browser_* in the Cloud Browser to execute the steps, which is not the same as alternative-selection guidance.

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