Skip to main content
Glama
GeiserX

cashpilot-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Docker Compose export

get_compose
Read-onlyIdempotent

Generates a docker-compose.yml to run one catalog service outside CashPilot, with credential placeholders; it does not deploy, so use deploy_service for deployment.

Instructions

A docker-compose.yml (YAML text) that runs one catalog service outside CashPilot, with placeholders for its credentials. Nothing is deployed; use deploy_service for that.

Input Schema

NameRequiredDescriptionDefault
archNoCPU architecture of the target machine: amd64, arm64 (Raspberry Pi 4/5, Apple silicon) or arm (32-bit). Default: the catalog's default image, which is amd64.
slugYesService to export. Lowercase catalog slug, e.g. "honeygain"; list_deployed_services and list_available_services show them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / arch
      Added value: +{
+  "description": "CPU architecture of the target machine: amd64, arm64 (Raspberry Pi 4/5, Apple silicon) or arm (32-bit). Default: the catalog's default image, which is amd64.",
+  "enum": [
+    "amd64",
+    "arm64",
+    "arm"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / slug / description
      Previous value: -"Service slug identifier"New value: +"Service to export. 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}$"
  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 declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: the output is YAML text, it is a template with credential placeholders rather than working secrets, and no deployment occurs. Only gap is that it doesn't say how the arch parameter changes the emitted YAML.

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?

One sentence splitting output form, scope, and the sibling redirect. Front-loaded with the artifact type and zero filler.

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 description usefully characterizes the return value as YAML text with credential placeholders. The arch parameter's effect on the emitted file is left entirely to the schema, a minor gap for an export tool.

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 both params (slug, arch) are fully documented in the schema with enum values and defaults. The description adds nothing param-specific beyond noting credential placeholders, so the 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 and artifact: produces a docker-compose.yml (YAML text) for one catalog service running outside CashPilot. That is clearly distinct from deploy_service and from any of the lifecycle siblings, so an agent can route without opening the schema.

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?

Names the condition that selects the sibling: 'Nothing is deployed; use deploy_service for that.' The use case (running the service outside CashPilot) is stated, so the when-to-use is clear even though no explicit when-not besides deployment is spelled out.

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