Skip to main content
Glama

Deploy app

deploy

Safety-check and deploy an owned project as a new version (Versions page). database: true represents the human’s agreement to a managed database for this exact projectId; a managed database is part of the Pro plan, and of the account’s plan where it includes one, and runs until deleted. Omitted adds none the human has not agreed to; false adds none. summary titles it; never a secret. When available, the result records anonymous reachability: publiclyReachable at verification.checkedAt, not visitor-response deployment identity; serving and servingDeploymentId are committed selection, managedUrl/url the app address, and protection an access gate, not a build failure. A note alone is no failure; queued/building attempts are pending, and a restored selection with an unconfirmed visitor-version note is settled. ready is the connection settings, never the tables. mobileReadiness: metadata, not a verdict.

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": {
      "projectId": "<projectId>"
    },
    "name": "deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNo
summaryNo
databaseNo
projectIdYes

Output Schema

NameRequiredDescriptionDefault
urlYes
noteNo
titleNo
sourceNo
statusYes
servingNo
databaseNo
providerYes
projectIdNo
laneActionNo
managedUrlNo
failureCodeNo
deploymentIdYes
newerAttemptNo
sourceOriginNo
verificationNo
appAttributionNo
mobileReadinessNo
publiclyReachableNo
servingDeploymentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare a non-read-only, open-world, non-idempotent, non-destructive operation; the description adds critical side-effect and result-state context, including managed-database persistence and how to interpret serving/protection/note/pending fields. That is substantial disclosure beyond annotations, with no contradiction.

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

Conciseness3/5

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

The purpose is front-loaded, but the remainder is a dense semicolon-heavy block of output-field caveats, some of which overlap with the output schema and are hard to scan. It is informative but not concise or well-structured.

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 deployment tool with an output schema and annotations covering safety, the description supplies the key hidden semantics: database side effects, summary sensitivity, and failure-state interpretation. It is nearly complete, though it omits region guidance and explicit permission/auth prerequisites.

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?

With schema coverage at 0%, the description must carry parameter meaning; it explains database semantics thoroughly and says summary titles the version and must not be a secret, and ties database to projectId. It leaves the region parameter's selection semantics unexplained and only indirectly describes projectId, so compensation is partial.

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 opening clause names a specific action (safety-check and deploy), resource (owned project), and outcome (new version), so an agent knows this is deployment rather than database or sharing operations. It does not explicitly distinguish itself from sibling tools such as databaseCreate or builderLink, keeping it at 4.

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?

The only usage context is implicit in 'deploy an owned project as a new version'; the description never states when to choose deploy over sibling operations or any when-not conditions. It gives parameter behavior but not alternative routing, so it is minimum viable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources