Skip to main content
Glama

Schedule job in CrewNest

crewnest_schedule_job
Read-onlyIdempotent

Schedule 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_schedule_job"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real value beyond the annotations by disclosing the counterintuitive behavior: the tool opens nothing and only returns screens/buttons/fields, and the actual change happens through separate browser tools. This resolves what would otherwise look like a readOnly 'schedule' contradiction. The closing sentence about CrewNest's external Job Pricing MCP server is tangential and doesn't describe this tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action and the key caveat ("opens nothing by itself") efficiently across clear sentences. The final sentence about the official API and Job Pricing MCP server is unrelated to scheduling and reads as promotional padding.

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 0-param, annotation-covered, no-output-schema tool, the description supplies what matters: the return is instructional, not a live mutation, and a follow-up path exists. Minor gap is the lack of guidance on non-browser alternatives or sibling scheduling tools.

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?

Zero parameters and 100% schema coverage, so the baseline is high. The description adds no field-level detail, but none is needed for a no-arg 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 ("Schedule job in the user's own CrewNest account") and then clarifies the surprising part: it returns step-by-step guidance rather than performing the action. It does not explicitly distinguish itself from siblings like crewnest_reschedule_job or crewnest_schedule_recurring_visit, so the agent still has to reason about which scheduling tool fits.

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?

Gives a clear workflow prescription: use this first to get the instructions, then execute with the cotlet_browser_* tools in the Cloud Browser. It lacks explicit exclusions (e.g., when to prefer a sibling scheduler instead), so it is strong context without full when-not guidance.

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