Skip to main content
Glama
GeiserX

cashpilot-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Start service

start_service
Idempotent

Starts a deployed service's stopped container on one worker, leaving running services unchanged.

Instructions

Start a deployed service's stopped container on one worker. Starting a running service changes nothing.

Input Schema

NameRequiredDescriptionDefault
slugYesService to start. 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 start. 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.6/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is covered structurally. The description's "Starting a running service changes nothing" essentially restates idempotency, and it adds little beyond that — nothing about permissions, failure behavior, or what happens if the service is not deployed.

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 with the action front-loaded and the no-op caveat second; nothing is wasted or buried.

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 simple idempotent, non-destructive start operation with full schema coverage and no output schema, the description covers the core behavior. A note on what a failed start returns or whether the container is created vs reused would close the remaining gap.

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%, with slug, instance, and worker_id each documented including fallback rules for a single online worker. The description adds only the framing "on one worker," which the worker_id schema text already conveys, so 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 names a specific verb and resource ("Start a deployed service's stopped container") plus the scope ("on one worker"), so the agent knows exactly what operation is performed. It does not explicitly distinguish itself from restart_service or deploy_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?

"Starting a running service changes nothing" gives a useful condition (no-op if already running) that implies when this is appropriate. However, it never names the alternatives (restart_service for a running service, deploy_service when not yet deployed), so the agent must infer the routing.

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