Skip to main content
Glama

start-application

Start a Coolify application using its UUID to initiate and make it available for use.

Instructions

Start a specific application using its UUID. This initiates the application and makes it available for use.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesResource UUID

Implementation Reference

  • Handler for the 'start-application' tool. Parses the UUID from input arguments, calls the Coolify API endpoint `/applications/${uuid}/start`, and returns the JSON response as text content.
    case "start-application": {
      const { uuid } = UuidSchema.parse(request.params.arguments);
      const result = await coolifyApiCall(`/applications/${uuid}/start`);
      return {
        content: [{
          type: "text",
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • src/index.ts:98-102 (registration)
    Registration of the 'start-application' tool in the list-tools response, defining its name, description, and input schema.
    {
      name: "start-application",
      description: "Start a specific application using its UUID. This initiates the application and makes it available for use.",
      inputSchema: zodToJsonSchema(UuidSchema),
    },
  • UuidSchema defines the input structure for the tool: an object with a 'uuid' string field, used by multiple tools including start-application.
    const UuidSchema = z.object({
      uuid: z.string().describe("Resource UUID"),
    });
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool 'initiates the application' but doesn't specify whether this requires specific permissions, what happens if the application is already running, whether it's idempotent, or what the expected response looks like. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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

Conciseness4/5

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

The description is appropriately concise with two sentences that directly address the tool's purpose and outcome. It's front-loaded with the core action and avoids unnecessary elaboration, though it could potentially benefit from slightly more structured guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'makes it available for use' means operationally, what happens on failure, or what the agent should expect as a result. Given the complexity of starting applications and the lack of structured behavioral data, more context is needed.

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 the single parameter 'uuid' documented as 'Resource UUID'. The description adds that it's for 'a specific application using its UUID', which provides context about what type of resource this UUID refers to, but doesn't offer additional syntax, format, or validation details beyond what the schema already provides.

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 clearly states the action ('Start') and target resource ('a specific application using its UUID'), with the outcome ('initiates the application and makes it available for use'). It distinguishes from siblings like 'stop-application' or 'restart-application' by specifying the start action, but doesn't explicitly differentiate from 'deploy' or 'update-application' which might also initiate applications.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'deploy', 'restart-application', or 'update-application'. It doesn't mention prerequisites (e.g., application must be stopped), exclusions, or typical use cases, leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/StuMason/coolify-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server