Skip to main content
Glama

Reschedule job in CrewNest

crewnest_reschedule_job
Read-onlyIdempotent

Reschedule job 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_reschedule_job"
  }
}

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=true and destructiveHint=false, and the description reinforces this by stating the tool opens nothing and only returns instructions. That workflow detail (returns screens, buttons, fields; hands off to browser tools) is genuinely useful context beyond the annotations. The closing sentence about CrewNest's official Job Pricing MCP server does not describe this tool's behavior and reads as unrelated promotion.

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 core is front-loaded and efficient, but the final sentence about CrewNest's official free Job Pricing MCP server is unrelated to invoking this tool and dilutes focus. The phrase "from ChatGPT, Claude or any AI agent" is redundant padding in an MCP context.

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 guidance tool with no output schema, the description covers what is returned (step-by-step screens, buttons, fields) and what happens next (use cotlet_browser_*). What is missing is minor: no indication of prerequisites such as an authenticated CrewNest session before the browser handoff.

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 the baseline is 4 and there is no parameter meaning for the description to add. The description correctly implies a parameterless guidance call, and nothing is misrepresented.

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 verb and resource ("Reschedule job") and makes clear the tool returns step-by-step instructions rather than performing the action. It distinguishes itself from the action-performing path by pointing to the cotlet_browser_* tools, though it does not contrast with nearby siblings like crewnest_schedule_job or crewnest_configure_recurring_job.

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?

It gives a clear usage context: call this to get the CrewNest UI steps, then execute them with cotlet_browser_* in the user's Cloud Browser. It explicitly says the tool "opens nothing by itself," which sets expectations. It stops short of stating when not to use it or how it differs from rescheduling-adjacent siblings.

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