Skip to main content
Glama

nsd_delete_site

Delete a site and all its versions. Requires the site id (never a name). The address becomes free for anyone.

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_id": "<site_id>",
      "confirm": "<confirm>"
    },
    "name": "nsd_delete_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true.
site_idYes

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?

With no annotations supplied, the description carries the full burden, and it does disclose significant behavior beyond the schema: deletion cascades to all versions and the address is released for anyone to reuse. It stops short of covering permissions/auth needs, whether the operation is reversible, or what happens with a nonexistent id.

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 action, then the id constraint, then the consequence. No filler and nothing buried.

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 two-parameter destructive tool with no annotations and no output schema, the definition covers purpose, cascade effect, id form, and side effect. Only auth prerequisites and irreversibility are left implicit.

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?

Schema coverage is only 50% (site_id is undocumented in the schema), and the description compensates by specifying that it must be an id, never a name. The 'confirm' semantics are already handled by the schema's 'Must be true', so nothing is missing there.

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, resource, and blast radius: 'Delete a site and all its versions.' The cascade note plus the 'site id (never a name)' constraint is enough to distinguish it from siblings like nsd_get_site or nsd_update without opening their schemas.

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?

Usage is implied by the destructive verb, and there is a real precondition ('Requires the site id'), but no explicit when-to-use vs. alternatives (e.g., nsd_update for changes that are not deletions) and no when-not-to-use or warning about checking the site first.

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.