Skip to main content
Glama

End recurring service in CrewNest

crewnest_end_recurring_service
Read-onlyIdempotent

End recurring service 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_end_recurring_service"
  }
}

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 it "opens nothing by itself" and only returns screens, buttons, and fields. That is meaningful added context about what the call actually produces and does not do. It stops short of describing the output structure or error behavior, but the safety profile is unambiguous.

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 two clauses are front-loaded and useful, but the trailing sentence about CrewNest's official Job Pricing MCP server with three read-only tools is unrelated to ending a recurring service and does not help the agent decide or invoke this tool. That sentence dilutes 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, read-only guidance tool with no output schema, the description covers what it returns (step-by-step screens, buttons, fields), what it does not do, and which tools complete the task. The only missing piece is a rough sense of the response shape or how to handle a failure to find the workflow.

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?

There are zero parameters, so the baseline is 4. Nothing in the description needs to explain input semantics, and it correctly implies no arguments are required.

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 verb and resource ("End recurring service in the user's own CrewNest account") and immediately clarifies the actual deliverable: step-by-step instructions rather than a mutation. That clarification is essential because the tool name implies an action. It does not distinguish itself from close siblings such as crewnest_pause_recurring_job or crewnest_list_recurring_services.

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 explicit workflow guidance: call this to get the manual steps, then perform them with cotlet_browser_* tools in the user's CrewNest Cloud Browser. That is actionable routing information an agent would otherwise have to guess. There is no guidance on when to prefer pausing vs ending a recurring service, which is the main exclusion gap.

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