Skip to main content
Glama
GeiserX

cashpilot-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Stop service

stop_service
DestructiveIdempotent

Stops a deployed service's container on a worker to halt earnings while keeping its configuration and data intact for restart.

Instructions

Stop a deployed service's container on one worker. The service earns nothing until start_service runs; configuration and data are kept.

Input Schema

NameRequiredDescriptionDefault
slugYesService to stop. Lowercase catalog slug, e.g. "honeygain"; list_deployed_services and list_available_services show them.
instanceNoWhich copy of the service on that worker, 1 to 10. Default 1.
worker_idNoWorker (server) to act on, from list_workers. Required when more than one worker is online; with a single online worker CashPilot picks it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / instance
      Added value: +{
+  "description": "Which copy of the service on that worker, 1 to 10. Default 1.",
+  "maximum": 10,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / slug / description
      Previous value: -"Service slug identifier"New value: +"Service to stop. Lowercase catalog slug, e.g. \"honeygain\"; list_deployed_services and list_available_services show them."
    • addedInput schema / properties / slug / pattern
      Added value: +"^[a-z0-9][a-z0-9._-]{0,63}$"
    • addedInput schema / properties / worker_id
      Added value: +{
+  "description": "Worker (server) to act on, from list_workers. Required when more than one worker is online; with a single online worker CashPilot picks it.",
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, which could make an agent fear permanent loss. The description resolves that by stating configuration and data are kept, materially lowering the perceived blast radius, and it confines the action to one worker. It doesn't mention auth needs or what happens to in-flight work.

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

Conciseness5/5

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

Two short sentences, zero padding, and the scope statement is front-loaded before the consequence. Nothing is redundant with the title beyond the necessary verb.

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?

With no output schema, the agent gets enough: the action is scoped, reversible via start_service, and non-destructive to data. It doesn't say what the call returns (e.g., confirmation or resulting state), which is a minor gap for a mutation with no return contract.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so slug, instance, and worker_id are fully documented in the schema, including their enumeration sources. The description's only contribution is the "on one worker" scoping, which is already conveyed by worker_id, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (stop) and a precisely scoped resource (a deployed service's container on one worker). It also names the counterpart operation start_service, so an agent can separate it from restart_service or remove_service without opening schemas.

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 service earns nothing until start_service runs" gives a clear condition and names the reversing action, which is exactly what an agent needs before pausing a service. It stops short of explicitly excluding remove_service for permanent deletion, so the when-not case is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools