Skip to main content
Glama

Press5 launch pad

Delete a site

delete_site
DestructiveIdempotent

Delete a site and all its deploys. It goes offline at once and the name becomes free for anyone. Ask the person first.

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": {
      "site": "<site>",
      "confirm": "<confirm>"
    },
    "name": "delete_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
tokenNoA press5 token (p5_...). Only needed when the MCP connection has no Authorization header, e.g. right after login_check.
confirmYesMust be true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond destructiveHint=true by spelling out consequences annotations cannot express: the site goes offline immediately, all deploys are removed, and the name becomes claimable by anyone. That last point is a real, non-obvious risk. It does not say whether the action can be undone or what the response contains, which keeps it below a 5.

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?

Three short sentences, front-loaded with the effect, then the consequence, then the human-confirmation instruction. No filler or repetition.

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 three-parameter destructive tool with rich annotations and no output schema, the description covers target, impact and the confirm-first rule. The only gap is that it never explains when the token parameter is needed or what happens after deletion succeeds.

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 67% and the 'site' and 'confirm' parameters are already described in the schema. The description only indirectly reinforces the target ('a site') and never mentions the conditional token parameter, so it adds little semantic detail beyond the structured fields.

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 and resource ('Delete a site') plus the blast radius ('and all its deploys'), which is more than the title alone and clearly separates it from deploy_site, rollback_site and site_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives an explicit precondition — 'Ask the person first' — which is exactly the guidance an agent needs before an irreversible action, and the preceding sentence explains why (immediate offline, name freed). No exclusion or alternative path is named, but none of the listed siblings performs a comparable operation.

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