Skip to main content
Glama

create-app

Deploy applications on Koyeb by specifying a name to automate cloud infrastructure setup and management.

Instructions

Create an app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes

Implementation Reference

  • The createApiTool function creates the actual handler for the create-app tool. It takes 'createApp' as the name parameter, retrieves the corresponding function from the @koyeb/api-client-js package, and returns an async callback that invokes the API with authentication and parameters, returning the result as text content.
    export function createApiTool(name: keyof Koyeb): ToolCallback<ZodRawShape> {
      const fn = koyeb[name] as Function;
    
      return async (params: object) => {
        const result = await fn({ auth, ...params });
    
        if (result.error) {
          return createTextContent('Error: ' + result.error ? JSON.stringify(result.error) : 'unknown error');
        }
    
        return createTextContent(JSON.stringify(result.data));
      };
    }
  • The schema for create-app is defined inline using Zod. It expects a body object with a required 'name' string field that describes the app name.
    server.tool(
      'create-app',
      'Create an app',
      {
        body: z.object({
          name: z.string().describe('The name of the app'),
        }),
      },
      createApiTool('createApp'),
    );
  • src/tools/app.ts:6-41 (registration)
    The app() function exports and registers all app-related tools including 'create-app' on the MCP server. This function is called from src/index.ts to initialize the tools.
    export function app(server: McpServer) {
      server.tool(
        'list-apps',
        'List apps',
        {
          query: z.object({
            limit: z.string().optional().describe('The number of items to return'),
            name: z.string().optional().describe('A filter for name'),
            offset: z.string().optional().describe('The offset in the list of item to return'),
          }),
        },
        createApiTool('listApps'),
      );
    
      server.tool(
        'get-app',
        'Get an app by its id',
        {
          path: z.object({
            id: z.string().describe('The id of the App'),
          }),
        },
        createApiTool('getApp'),
      );
    
      server.tool(
        'create-app',
        'Create an app',
        {
          body: z.object({
            name: z.string().describe('The name of the app'),
          }),
        },
        createApiTool('createApp'),
      );
    }
  • src/index.ts:28-28 (registration)
    The main entry point calls app(server) to register the create-app tool along with other app-related tools on the MCP server instance.
    app(server);
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Create an app' implies a write/mutation operation, but the description doesn't disclose any behavioral traits: no information about permissions required, whether this is a destructive operation, what happens on success/failure, rate limits, or what the expected output might be. This is inadequate for a creation tool.

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 extremely concise at just two words. While this represents severe under-specification, from a pure conciseness perspective, it's maximally efficient with zero wasted words. Every word earns its place, though there are far too few words to be helpful.

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

Completeness1/5

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

Given this is a creation tool with no annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It doesn't explain what an 'app' is in this system, what happens after creation, what permissions are needed, or how this differs from related tools. The description fails to provide the minimal context needed for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, so the description must compensate. The description mentions no parameters at all, even though there's a required 'body' parameter with a nested 'name' property. The description doesn't explain what 'app' means in this context or what naming constraints might exist. It adds no value beyond what the bare schema structure provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create an app' is a tautology that essentially restates the tool name. While it does specify the verb ('create') and resource ('app'), it provides no additional context about what kind of app, in what system, or with what characteristics. It doesn't distinguish this tool from sibling tools like 'create-service' or 'deploy'.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance about when to use this tool versus alternatives. There are multiple sibling tools that could be related (create-service, deploy, list-apps, update-service), but the description offers no context about prerequisites, appropriate scenarios, or when other tools might be better choices.

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/samihalawa/mcp-server-koyeb'

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