Skip to main content
Glama

project_undeploy

DestructiveIdempotent

Undeploy a project — revokes its public subdomain and returns it to an inactive state. All data is preserved.

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": {
      "project_id": "<project_id>"
    },
    "name": "project_undeploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID, subdomain, or 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds meaningful context beyond that: the specific thing lost is the public subdomain, the resulting state is inactive, and all data survives. It stops short of noting whether the tool fails on an already-inactive project or affects in-flight deployments.

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?

One compact sentence that front-loads the action and immediately states the effect and the data-preservation guarantee. No filler, nothing redundant.

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 single-parameter mutation with full annotation and schema coverage, the description supplies the essential consequence (subdomain revoked, data intact). Only minor edge-case behavior — e.g. behavior on an already-undeployed project — is unstated.

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 single project_id parameter is documented in the schema itself, including the accepted subdomain/'default' forms. The description adds nothing about parameter meaning, which is fine at this coverage level.

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?

States a specific verb and resource ('Undeploy a project') and then defines the concrete effect: revokes the public subdomain and returns the project to an inactive state. This implicitly separates it from project_delete (data preserved) without naming the sibling, so it is clear but not fully differentiated.

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 'data is preserved' clause implies this is the right choice when you want to take a project offline without destroying it, but the description never explicitly says when to use this versus project_delete, project_archive, or project_deploy. Usage must be inferred.

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