Skip to main content
Glama

List recurring services in CrewNest

crewnest_list_recurring_services
Read-onlyIdempotent

List recurring services 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_list_recurring_services"
  }
}

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, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds non-obvious behavior beyond them: it does not read data itself, it returns procedural guidance (screens, buttons, fields), and it opens nothing on its own, so the agent knows a browser tool is required to complete the task. It omits whether the returned guidance is paginated or complete, but the core behavioral surprise is disclosed.

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 first two sentences are front-loaded and earn their place: what it does, that it opens nothing, and which tools to follow with. The trailing sentence about CrewNest's official Job Pricing MCP server is tangential to invoking this tool and reads as promotional filler that dilutes the 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 listing tool with no output schema and already-rich annotations, the description covers purpose, the advisory-only nature of the response, and the required follow-up tooling. The only gap is that it does not describe the shape of the returned step-by-step guidance, which matters somewhat given there is no output schema.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema is empty and non-permissive (additionalProperties=false), and the description correctly implies no inputs are needed.

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 ("List recurring services in the user's own CrewNest account") and scopes it to the caller's own account, which distinguishes it from the mutation siblings like crewnest_configure_recurring_job and crewnest_end_recurring_service. It does not explicitly name a list-type sibling to differentiate from (crewnest_list_jobs, crewnest_list_crew), but the recurring-services scope is clear.

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?

The description gives a clear usage context: it returns step-by-step instructions for doing it in CrewNest and explicitly says to then perform it with the cotlet_browser_* tools in the Cloud Browser. That is a real when-to-use/with-what rule. It stops short of stating when NOT to use it or naming a concrete alternative among the crewnest_list_* 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