Skip to main content
Glama
dfridkin

clawops

by dfridkin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Provision and Deploy Stack

clawops_up
DestructiveIdempotent

Provision and deploy a complete clawops stack after plan approval. Re-running without spec changes creates no diff, and progress notifications keep you updated.

Instructions

Provision and deploy a clawops stack. Idempotent — re-running with no spec change produces no diff. Long-running (median 3min, p99 8min) so emits progress notifications per R12.

Use when: the user explicitly asks to deploy, provision, create, or "spin up" a stack. Always after the user has reviewed a plan (clawops_plan first when in doubt).

Do NOT use when: the user has not yet generated a plan and is in exploratory/discovery mode — use clawops_plan first. Do NOT use for an existing stack you only need to update; refresh first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoShow what would be created and change nothing. Use this first when the user has not yet approved a spend
regionNoCloud region to deploy into, in the provider's own spelling (us-east-1, us-central1, eastus). Omitted = the region recorded for the stack
sshCidrNoCIDR(s) allowed to reach SSH, comma-separated, or 'auto' for the caller's own address. Omitted means none, and nothing will be able to connect — including every clawops day-two command.
providerNoDefaults to provider configured for this stack
stackNameNoName for the stack to provision, and the name every later command refers to it by. Omitted = the default stack in ~/.clawops/config.json
gatewayCidrNoCIDR(s) allowed to reach the gateway port. Requires publishGateway=all.
instanceTypeNoA clawops size (micro|small|medium|large|gpu) or a provider-native machine type. Not an enum: Azure offers SKU families per subscription, and an account offered none of the five sizes clawops names would otherwise have no way to deploy. small
publishGatewayNoWhich interface the gateway binds. 'all' serves plaintext HTTP.
openclawVersionNosemver or 'stable'/'dev'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.1.3
    • addedInput schema / properties / dryRun / description
      Added value: +"Show what would be created and change nothing. Use this first when the user has not yet approved a spend"
    • addedInput schema / properties / gatewayCidr / description
      Added value: +"CIDR(s) allowed to reach the gateway port. Requires publishGateway=all."
    • addedInput schema / properties / instanceType / description
      Added value: +"A clawops size (micro|small|medium|large|gpu) or a provider-native machine type.\nNot an enum: Azure offers SKU families per subscription, and an account offered\nnone of the five sizes clawops names would otherwise have no way to deploy.\n"
    • addedInput schema / properties / openclawVersion / description
      Added value: +"semver or 'stable'/'dev'"
    • addedInput schema / properties / provider / description
      Added value: +"Defaults to provider configured for this stack"
    • addedInput schema / properties / publishGateway / description
      Added value: +"Which interface the gateway binds. 'all' serves plaintext HTTP."
    • addedInput schema / properties / region / description
      Added value: +"Cloud region to deploy into, in the provider's own spelling (us-east-1, us-central1, eastus). Omitted = the region recorded for the stack"
    • addedInput schema / properties / sshCidr / description
      Added value: +"CIDR(s) allowed to reach SSH, comma-separated, or 'auto' for the caller's own\naddress. Omitted means none, and nothing will be able to connect — including\nevery clawops day-two command.\n"
    • addedInput schema / properties / stackName / description
      Added value: +"Name for the stack to provision, and the name every later command refers to it by. Omitted = the default stack in ~/.clawops/config.json"
  2. First observedv2.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already provide idempotentHint and destructiveHint, but the description adds concrete behavior: idempotency detail ('no diff'), long-running timing (median 3min, p99 8min), and progress notifications. This is valuable context beyond the annotations, though it does not explicitly describe side effects on spec changes.

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?

The description is well-structured and front-loaded: core function first, then idempotency and timing, then usage guidance. Every sentence adds value, and it is not verbose despite covering multiple aspects.

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 9-parameter provisioning tool with no output schema, the description covers usage, alternatives, timing, and idempotency. It does not describe the return value, but given the lack of output schema and the presence of progress notifications, this is acceptable and likely sufficient for correct invocation.

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 the schema already documents all 9 parameters. The description does not add parameter-specific meaning beyond referencing plan usage; it meets the baseline but does not elevate it.

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?

The description states a specific verb+resource ('Provision and deploy a clawops stack') and differentiates from siblings by explicitly naming clawops_plan for planning and refresh for updates. It is unambiguous about what this tool does versus alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit 'Use when' and 'Do NOT use when' conditions, naming alternatives (clawops_plan, refresh) and the decision criteria (explicit deploy request, plan reviewed, exploratory mode). This is exemplary guidance.

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