Skip to main content
Glama

Download estimate pdf in CrewNest

crewnest_download_estimate_pdf
Read-onlyIdempotent

Download estimate pdf 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_download_estimate_pdf"
  }
}

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, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context beyond that: the tool performs no side effect ('opens nothing by itself'), returns procedural guidance rather than data, and must be paired with browser tools to complete the action. Missing only details like whether output is plain text or structured steps.

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 well-structured and front-loaded with scope, the no-side-effect caveat, and the follow-up tool family. The closing sentence about CrewNest's official Job Pricing MCP server is unrelated to downloading an estimate PDF and reads as promotional filler that 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, annotation-covered instruction tool with no output schema, the description supplies what an agent actually needs: the return is step-by-step UI guidance, and the real action requires cotlet_browser_* tools. Remaining gaps are minor — it does not say what the steps look like or what happens if the estimate is not accessible in the session.

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 meaning to convey; baseline 4 applies. The description correctly does not invent parameter discussion, though it also does not say how the target estimate is identified — implicitly via the browser session rather than arguments.

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 specific resource (estimate PDF) and states the exact nature of the operation: it 'Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself.' That differentiates it from the actual download tooling by clarifying it only produces instructions. It loses a point because the name says 'download' while the body says it downloads nothing, forcing the agent to reconcile a mild naming/behavior mismatch.

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?

Explicit sequencing guidance is given: call this first, then 'do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser.' That is a clear when-to-use-plus-next-step instruction. It does not exclude any sibling or state preconditions (e.g., whether the estimate must already exist), so it stops short of a 5.

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