Skip to main content
Glama

Optimize route in CrewNest

crewnest_optimize_route
Read-onlyIdempotent

Optimize route 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_optimize_route"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false. The description adds information annotations cannot convey: the return value is procedural guidance (screens, buttons, fields) and the tool "opens nothing by itself," so any real change requires a separate browser tool. That is exactly the kind of context that prevents an agent from assuming the route was already modified.

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 operative content is front-loaded and compact: purpose, return shape, non-execution caveat, and the browser-tool handoff. The trailing sentence about CrewNest's official free Job Pricing MCP server with three read-only tools is unrelated to invoking this tool and reads as promotional filler, diluting an otherwise tight definition.

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 tool with no output schema, the description covers what matters: what it returns, that it has no side effects, and how to complete the task afterward. The only omission is any hint of what the returned steps look like structurally or whether they vary by account state.

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 and the schema is an empty closed object, so there is nothing for the description to disambiguate. Baseline for a parameterless tool applies, and the description correctly does not invent argument syntax.

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 states a specific action and account scope ("Optimize route in the user's own CrewNest account") and then immediately clarifies the actual mechanic: it "Returns how to do it in CrewNest step by step (screens, buttons, fields) and opens nothing by itself." That reframes the name honestly, so an agent understands this is a guidance generator rather than an executing route editor. It never names a sibling, so it falls short of 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 Guidelines3/5

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

It gives a clear workflow context: use this to get the steps, "then do it with the cotlet_browser_* tools in the user's CrewNest Cloud Browser." That is real when-to-use guidance plus the execution handoff. However, it never says when NOT to use it, and it does not differentiate from route-adjacent siblings such as crewnest_reorder_route or crewnest_list_crew, leaving the agent to infer selection.

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