Skip to main content
Glama

SoFast

Delete a site

delete_site
DestructiveIdempotent

Sites cannot be deleted through this connection. Returns a link to the site's deletion form in the Sofast dashboard, where the account owner confirms the deletion themselves. Deletes nothing.

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

Input Schema

NameRequiredDescriptionDefault
siteYesThe site: its numeric id, its address (name.sofast.website or a custom domain) or its URL.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior1/5

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

The annotations declare destructiveHint=true and readOnlyHint=false, yet the description says the tool "Deletes nothing" and only mints a link. That is a direct conflict in the safety signal an agent depends on, and it leaves the true side-effect profile ambiguous.

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 most surprising and decision-relevant fact: deletion is not possible here. Nothing is padded or 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 one-parameter tool with no output schema, the description does the important work of explaining the return value (a link to the deletion form) and where confirmation happens. The only gap is the unresolved conflict with the destructiveHin annotation.

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 description coverage is 100% and the single 'site' parameter is fully documented in the schema (numeric id, address, or URL). The description adds no further meaning about the parameter, so the baseline of 3 applies.

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 outcome: it returns a link to the site's deletion form in the Sofast dashboard. It also explicitly rules out the action the name implies ("Sites cannot be deleted through this connection"), so an agent can distinguish it from create_site, publish_site, and the other siblings at a glance.

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?

It clearly establishes the condition for use: when a site needs to be deleted, this tool hands off the link because deletion itself only happens in the dashboard. It doesn't name a specific alternative sibling, but the handoff target (the dashboard form) is explicit.

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