Skip to main content
Glama
GeiserX

cashpilot-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Restart service

restart_service
Idempotent

Restart a deployed service container on a chosen worker while preserving its configuration and data. Earnings pause only while the container comes back online.

Instructions

Restart a deployed service's container on one worker, keeping its configuration and data. It stops earning for the few seconds the container needs to come back.

Input Schema

NameRequiredDescriptionDefault
slugYesService to restart. 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 restart. 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

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotent=true and destructive=false, and the description reinforces this with 'keeping its configuration and data'. It adds genuinely new behavioral context beyond the annotations: the brief earnings interruption while the container comes back up. It stops short of saying what happens on failure or if the service isn't currently running.

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 tight sentences with the operation front-loaded and the cost consequence second; nothing is redundant or padded.

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 full schema coverage and annotations covering safety and idempotency, the description only needs to convey behavior, which it does. The remaining gap is outcome handling — what is returned or what happens if the restart fails — though no output schema exists to carry that.

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 all three parameters are already fully documented with examples and constraints. The description's phrase 'on one worker' loosely gestures at worker_id but adds no new meaning to slug or instance, so the baseline 3 applies.

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 gives a specific verb and resource ('Restart a deployed service's container on one worker') plus the scope of the operation. It distinguishes itself implicitly from remove_service via 'keeping its configuration and data', but never explicitly names start_service or stop_service, which are the closest siblings.

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 only implied: an agent can infer that this is the tool for bouncing a running container without redeploying. The earnings-downtime note hints that restarts should not be gratuitous, but there is no explicit guidance on when to prefer start_service/stop_service or what precondition (service must be deployed) applies.

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