Skip to main content
Glama

Remind estimate in CrewNest

crewnest_remind_estimate
Read-onlyIdempotent

Remind 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_remind_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 the safety profile is covered structurally. The description adds real behavioral context beyond that: it explicitly says it 'opens nothing by itself' and that the return is a step-by-step walkthrough of screens, buttons and fields, telling the agent this is a planning/instruction artifact rather than an action. The trailing sentence about CrewNest's official Job Pricing MCP server adds nothing behavioral.

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 operational content is front-loaded and efficient - the return shape and the follow-up browser step come first. The final sentence about CrewNest's official free Job Pricing MCP server is unrelated marketing padding that does not help an agent select or invoke this tool, and the '(screens, buttons, fields)' parenthetical is redundant with the preceding 'step by step'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters, no output schema and full annotation coverage, the description needs only to explain what the returned guidance is for and how to apply it. It covers the how (browser tools afterward) but leaves the intent of 'remind' undefined and never says how the agent should identify the target estimate before acting, which is the main missing piece for a tool that has no inputs.

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 with an empty, fully closed schema, so there are no parameter semantics to explain. Baseline 4 applies. One could argue the absence of any identifier parameter (which estimate?) deserves comment, but that is a schema design issue, not a description gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the mechanism clearly (it returns step-by-step CrewNest instructions rather than performing anything), which separates it from action tools like crewnest_send_estimate. But the core business purpose of 'remind estimate' is never explained - it never says whether this nudges a customer about an outstanding estimate, reminds the owner to follow up, or something else. The verb+resource pair is restated from the title without being disambiguated.

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?

It gives a clear next-step instruction ('then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser'), which is genuinely useful routing. However, there is no when-to-use vs when-not guidance relative to siblings such as crewnest_send_estimate or crewnest_respond_to_estimate, and no prerequisites (must be signed in, which estimate to act on).

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