Skip to main content
Glama
Sign In
Hostsmith MCP Server

Hostsmith MCP Server

by hostsmith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

delete_site

Destructive

Permanently delete a site and all its deployed files. Action requires explicit user confirmation to prevent accidental data loss.

Instructions

Permanently delete a Hostsmith site and all of its deployed files. Destructive - only call after explicit user confirmation. The site URL becomes unreachable immediately and the content cannot be recovered. The user must pass confirm: true for the deletion to proceed; otherwise the call returns an error explaining the safeguard.

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

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe site ID to delete (from `list_sites` or `get_site`).
confirmNoSet to true only after the user has explicitly confirmed they want to permanently delete this site. Required safeguard - never pass true speculatively.
partitionNoData partition the site lives in. Omit to use the user's home partition.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.2

TDQS

A4.6/5.0
Behavior5/5

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

The description adds significant behavioral details beyond the destructiveHint annotation: the site URL becomes unreachable immediately, content cannot be recovered, and the confirm parameter must be true for the deletion to proceed. It also explains that omitting confirm returns an error.

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 description is two sentences long, front-loaded with the key purpose and a strong warning. Every sentence is informative and earns its place. No wasted words.

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?

Given no output schema, the description could mention what the response looks like on success or error. However, the behavioral information is well-covered. For a 3-parameter tool with low complexity, the description is mostly complete, lacking only a note about return values.

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?

With 100% schema coverage, baseline is 3. The description adds meaning by explaining the confirm parameter's safety purpose and that partition can be omitted for the home partition. It reinforces the confirm:true requirement, which is critical for safe usage.

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 clearly states it permanently deletes a Hostsmith site and all deployed files, specifying the verb 'delete', the resource 'site', and the scope 'all deployed files'. It distinguishes itself from sibling tools like create_site and get_site by being the only destructive deletion tool.

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?

The description explicitly warns that this is destructive and should only be called after explicit user confirmation. It also explains the confirm parameter safeguard. However, it does not mention specific alternatives (e.g., what to use if only temporary removal is needed), though in the tool's context the only appropriate alternative is not using the tool.

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