Skip to main content
Glama
Sign In
Kleap

Kleap

Official
by kleaphq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

create_app

Generate a live website from a plain-language description. Returns a task ID to monitor until the site is ready.

Instructions

Create a new Kleap website from a natural-language prompt. Returns a task — poll check_task until it completes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "create_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesWhat the website should be.
visibilityNo'public' (discoverable) or 'personal' (private).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Discloses that the tool returns a task (asynchronous) but does not mention authorization, rate limits, idempotency, or side effects. With no annotations, the description carries full burden and is adequate but not rich.

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 concise sentences: first states purpose, second gives actionable follow-up. No unnecessary words, front-loaded key information.

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 two-parameter tool with no output schema, the description covers creation and the subsequent polling action. It is complete enough to use correctly, though could hint at task ID usage.

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 coverage is 100%, and the description adds no additional meaning beyond what the input schema already provides for both parameters. Baseline 3 is appropriate.

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?

Clearly states it creates a Kleap website from a natural-language prompt and returns a task. The verb 'Create' and resource 'Kleap website' are explicit, and it distinguishes from sibling tools like modify_app and publish_app.

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?

Tells the user to poll check_task after creation, which is helpful for the follow-up. However, lacks explicit when-to-use or when-not-to-use guidance, and no alternatives are mentioned.

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