Skip to main content
Glama

Reorder route in CrewNest

crewnest_reorder_route
Read-onlyIdempotent

Reorder 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_reorder_route"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Adds genuinely useful disclosure beyond the annotations: it returns screens/buttons/fields and 'opens nothing by itself', which explains why readOnlyHint=true on an apparently mutating verb. Beyond that clarification it says nothing about whether the returned procedure is version-specific, how long it is, or what happens if the user's plan does not include routing — gaps that matter for a guidance tool with no output schema.

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-load the read-only nature plus the follow-up path. The third sentence, about CrewNest's separate Job Pricing MCP server, is unrelated marketing that gives an agent no help in selecting or invoking this tool and should be cut.

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 the essentials: what it returns (step-by-step screens, buttons, fields), that it performs no side effects, and how to act on the result. Only the distracting third sentence and the unaddressed overlap with the optimize-route sibling keep it from being 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?

Takes no parameters, so there is nothing for the description to disambiguate; the 100% schema coverage and empty properties object are consistent with the description. Baseline 4 applies for a zero-parameter tool.

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?

Names a specific verb and resource ('Reorder route in the user's own CrewNest account') and immediately clarifies that it returns step-by-step instructions rather than performing the reorder, which is essential given the action-sounding name. It does not explicitly contrast itself with the sibling crewnest_optimize_route, leaving the agent to infer which of the two route tools to pick.

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?

Establishes clear usage context: call this to obtain the CrewNest procedure, then execute it via the cotlet_browser_* tools in the user's Cloud Browser. What is missing is when NOT to use it, particularly versus the sibling optimize-route tool, so routing between route-related tools still requires inference.

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