Kleap

Check Build Status

check_task

Check a create/modify task. Returns quickly with the CURRENT status — report it to the user rather than calling again in the same turn; a build takes 5-15 min, so the answer to 'is it ready?' is usually 'still building, here is the progress'. The optional wait can shorten the hold but cannot exceed the server cap (8 seconds by default). status is one of: queued, processing, completed, failed, unknown_task (the id is unknown or aged out — that is an answer, not a failure: check the site itself with get_publish_status). On 'completed' the FILES are written; check deployment_status — 'pending' means the site is going live right now and production_url is still the PREVIOUS version, so say 'built, going live' and check once more in about a minute rather than reporting it stuck. 'deployed' means it is genuinely live. On 'failed': TASK_TIMEOUT/STALE_TASK = transient stall → retry_task (returns a NEW task_id to poll); TASK_FAILED = read error.message, retry once. (Running out of usage is not a task failure — create/modify reject up front with 402 INSUFFICIENT_CREDITS.)

Input Schema

TableJSON Schema

Name	Required	Description
`wait`	No	Optional. Seconds to hold the connection before returning. Capped server-side at a few seconds so the call always comes back inside a single turn — asking for more has no effect. Leave it unset.
`context`	Yes	Why this call, in one short sentence. Used to improve the connector; never include credentials or personal data.
`task_id`	Yes	The task_id returned by create_app or modify_app

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`plan`	No
`slug`	No
`app_id`	No
`reason`	No
`result`	No
`status`	No
`palette`	No
`task_id`	No
`metadata`	No
`progress`	No
`preview_url`	No
`production_url`	No
`screenshot_url`	No
`deployment_status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Far exceeds the annotations: it discloses timing expectations (5-15 min builds), the wait cap, the full status enum, the distinction between 'completed' and 'deployed', the 'pending means production_url is stale' trap, and which errors are transient vs terminal. This is exactly the operational context a poller needs.

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?

Front-loads the core answer ('returns quickly, report it') before the status semantics, and every clause carries operational value. It is dense and parenthetical-heavy, but trimming would lose actionable guidance rather than filler.

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

Completeness5/5

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

An output schema exists, so return shapes need not be described, yet the description still decodes the status values and deployment states that an agent most needs to interpret them. Nothing required to call and correctly report this tool is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning beyond it: why `wait` exists, that the server cap makes larger values no-ops, and the 'leave it unset' guidance. It does not restate the task_id origin beyond what the schema already says.

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+resource ('Check a create/modify task') and immediately scopes the return ('CURRENT status'), which cleanly separates it from retry_task and get_publish_status. An agent can identify this as the polling endpoint 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 Guidelines5/5

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

Gives explicit when-to-use, when-not-to-repeat ('report it to the user rather than calling again in the same turn'), and routes to named alternatives: retry_task for TASK_TIMEOUT/STALE_TASK, get_publish_status for unknown_task. Failure handling and the 402 credit case are spelled out.

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

All Kleap tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.