Skip to main content
Glama

Pause recurring job in CrewNest

crewnest_pause_recurring_job
Read-onlyIdempotent

Pause recurring 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_pause_recurring_job"
  }
}

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, and the description is consistent with them while adding real value: it clarifies that the tool "opens nothing by itself" and returns screens, buttons and fields rather than mutating state. The trailing note about CrewNest's separate Job Pricing MCP server adds no behavioral information about this tool.

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 compact, but the final sentence about CrewNest's official free Job Pricing MCP server is promotional, unrelated to selecting or invoking this tool, and dilutes the message. Removing it would leave a tight two-sentence 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, read-only guidance tool with no output schema, the description covers what matters: the action being guided, that nothing is opened, the shape of the returned instructions, and the companion tools that actually perform the change. Only the relationship to sibling recurring-service operations is left unstated.

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 fully closed, so there is no parameter meaning to convey. Baseline for a parameterless tool applies, with no offsetting gap.

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 ("Pause recurring job") and scopes it to "the user's own CrewNest account", which separates it from listing/configuring siblings. It does not explicitly differentiate from close alternatives such as crewnest_end_recurring_service or crewnest_cancel_job, leaving the pause-vs-end boundary to inference.

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 implies the correct workflow by stating the tool returns step-by-step instructions and that the actual pause is performed with the cotlet_browser_* tools. However, there is no explicit statement of when to choose this over ending or canceling a recurring service, and no prerequisites or failure conditions are given.

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