Skip to main content
Glama
purpleax

Fastly NGWAF MCP Server

by purpleax

delete_site

Remove a web application from Fastly's Next-Gen WAF protection by deleting its site configuration using corporation and site name parameters.

Instructions

Delete a site

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
corpNameNoCorporation name (uses context default if not provided)
siteNameNoSite name (uses context default if not provided)

Implementation Reference

  • Handler for the 'delete_site' tool: resolves corporation and site names from context or arguments, validates siteName, calls the client.deleteSite method, and assigns the result.
    case 'delete_site':
        const { corpName: corpForDelete, siteName: siteForDelete } = resolveContext(typedArgs);
        if (!siteForDelete) {
            throw new Error('Site name is required. Please set context or provide siteName parameter.');
        }
        result = await client.deleteSite(corpForDelete, siteForDelete);
        break;
  • Helper method in FastlyNGWAFClient class that performs the actual API deletion of a site by sending a DELETE request to the Fastly NGWAF API.
    async deleteSite(corpName, siteName) {
        await this.api.delete(`/corps/${corpName}/sites/${siteName}`);
        return { success: true };
  • server.js:524-534 (registration)
    Tool registration in the tools array, including name, description, and input schema. This is returned by the ListTools handler.
    {
        name: 'delete_site',
        description: 'Delete a site',
        inputSchema: {
            type: 'object',
            properties: {
                corpName: { type: 'string', description: 'Corporation name (uses context default if not provided)' },
                siteName: { type: 'string', description: 'Site name (uses context default if not provided)' },
            },
        },
    },
  • Input schema definition for the delete_site tool, specifying corpName and siteName as optional string parameters.
    inputSchema: {
        type: 'object',
        properties: {
            corpName: { type: 'string', description: 'Corporation name (uses context default if not provided)' },
            siteName: { type: 'string', description: 'Site name (uses context default if not provided)' },
        },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Delete a site', implying a destructive mutation, but doesn't disclose critical behaviors: whether deletion is permanent, requires confirmation, affects related data, has rate limits, or needs specific authentication. This leaves significant gaps for a tool that performs deletion.

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 a single, direct sentence 'Delete a site' with zero wasted words. It is appropriately sized for a simple tool and front-loaded with the core action, making it highly efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (destructive deletion with 2 parameters) and lack of annotations or output schema, the description is incomplete. It doesn't cover behavioral aspects like permanence, side effects, or error handling, which are crucial for safe invocation. The schema covers parameters well, but overall context is insufficient for a mutation tool.

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%, with parameters 'corpName' and 'siteName' documented as using context defaults if not provided. The description adds no additional meaning beyond the schema, such as format examples or constraints, so it meets the baseline of 3 where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a site' states the action (delete) and resource (site), which provides a basic purpose. However, it doesn't differentiate from sibling tools like 'delete_corp_rule' or 'delete_site_rule', nor does it specify what kind of site (e.g., web, physical) or scope, making it vague beyond the minimal definition.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'update_site' or 'list_sites', nor any prerequisites (e.g., site must exist, permissions required). The description only states what it does, not when or why to invoke it, leaving the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/purpleax/FastlyMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server