Skip to main content
Glama

Schedule recurring visit in CrewNest

crewnest_schedule_recurring_visit
Read-onlyIdempotent

Schedule recurring visit 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_recurring_visit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is known. The description still adds real behavioral substance beyond that: it explicitly states the tool 'opens nothing by itself' and returns procedural guidance instead, and it names the follow-on mechanism (cotlet_browser_* in the user's CrewNest Cloud Browser). That is genuinely helpful context an agent could not infer from the annotations alone. It stops short of describing auth requirements or what the step-by-step payload looks like.

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 core is front-loaded and reasonably tight: what it returns, that it performs nothing itself, and which tool class to use next. The final sentence about CrewNest publishing a separate free Job Pricing MCP server is unrelated promotional content that does not help an agent select or invoke this tool and dilutes the signal. A single irrelevant sentence in an otherwise compact description warrants a middle score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 and full annotation coverage, the description covers the essentials: it is a lookup of procedural steps, it mutates nothing, and the actual execution happens through browser tools. It is not complete in the sense of routing, however — with siblings like crewnest_schedule_recurring_visit-adjacent tools (schedule_job, configure_recurring_job) present, an agent still lacks the criteria to pick this one, and there is no hint about what the returned steps contain or whether they can be partially satisfied.

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 and the schema is an empty object, so there is no parameter semantics for the description to elaborate on. Baseline 4 applies. The description correctly implies the tool needs no input to produce the guide, though it never says so explicitly.

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 concrete verb and resource (schedule a recurring visit) and, importantly, clarifies that the tool returns step-by-step instructions (screens, buttons, fields) rather than performing the action. This resolves the ambiguity that would otherwise come from a name that reads like a mutation. It does not, however, distinguish itself from near-name siblings such as crewnest_configure_recurring_job or crewnest_schedule_job, leaving an agent to guess which of several scheduling-related tools is the guide versus the actor.

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?

Usage is implied rather than specified: the description says the output is a how-to and that the agent must then act with the cotlet_browser_* tools in the CrewNest Cloud Browser, which is a useful sequencing instruction. What is missing is any when-to-use-this-versus-an-alternative guidance, especially against the many sibling tools that appear to perform scheduling or recurring-job configuration directly. No exclusions or preconditions 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