Skip to main content
Glama
antideploy

antideploy-mcp

Official
by antideploy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Create the application's database now

database_create

Provisions the app's Postgres database during development so code is tested against the real database and reused at deploy. Safe to call twice; skip if an external database is already configured.

Instructions

Create this application's Postgres database now, while the project is still being written, so it is built and tested against the real thing instead of SQLite or mock data. A later deploy reuses it, so what was tested is what goes live. Safe to call twice. Skip it when the project stores nothing, or already points at a database the user chose (a DATABASE_URL in .env that is not localhost, or a provider they named): the answer is a 409 own_database. It counts against the plan's allowance; a 402 database_limit is not a rate limit, so do not retry, say what it says and let the user choose. If the call is refused or blocked, do not look for another route: tell the user, who can approve it or press Create database on the application's page in the console, then carry on with database_env_to_file. The connection string is not returned: call database_env_to_file to put it in .env. Tell the user what was created and on which account.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the sparse annotations, the description discloses idempotency, plan allowance impact, the meaning of a 402 database_limit error, refusal handling, and the fact that the connection string is not returned. These are important operational traits for a create 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 definition is dense but front-loaded with the core action and use case, followed by skip conditions, error handling, and follow-up steps. Every sentence carries operational value for a tool with no parameters but nontrivial workflow constraints.

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?

With no output schema and minimal annotations, the description still explains the key return limitation, error behavior, approval fallback, and the required next sibling call. It is complete enough for an agent to invoke and recover correctly.

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?

The tool has zero parameters, so there are no parameter semantics to document. The baseline for zero-parameter tools is 4, and nothing in the description suggests missing parameter information.

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?

The description states a specific verb and resource: create this application's Postgres database now. It also distinguishes the action from the follow-up sibling by noting the connection string is not returned and directing the agent to `database_env_to_file`.

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?

It gives explicit conditions for use and for skipping it, including projects that store nothing or already point at a user-chosen database. It also names the resulting 409 own_database state and routes the agent to `database_env_to_file` afterward.

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