Skip to main content
Glama
purpleax

Fastly NGWAF MCP Server

by purpleax

get_site

Retrieve configuration and security details for a specific web application site from Fastly's Next-Gen WAF to monitor and manage protection settings.

Instructions

Get details of a specific 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 logic for the 'get_site' MCP tool: resolves corporation and site names from context or arguments, validates siteName, and delegates to the FastlyNGWAFClient.getSite method to fetch site details.
    case 'get_site':
        const { corpName: corpForSite, siteName: siteForGet } = resolveContext(typedArgs);
        if (!siteForGet) {
            throw new Error('Site name is required. Please set context or provide siteName parameter.');
        }
        result = await client.getSite(corpForSite, siteForGet);
        break;
  • Input schema definition for the 'get_site' tool, specifying optional corpName and siteName parameters with descriptions.
    {
        name: 'get_site',
        description: 'Get details of a specific 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)' },
            },
        },
    },
  • Helper method in FastlyNGWAFClient class that performs the actual API GET request to retrieve site details from the Fastly NGWAF API.
    async getSite(corpName, siteName) {
        const response = await this.api.get(`/corps/${corpName}/sites/${siteName}`);
        return response.data;
    }
  • Utility function used by 'get_site' handler to resolve corpName and siteName from tool arguments or global context, with validation.
    function resolveContext(args) {
        const corpName = args.corpName || context.defaultCorpName;
        const siteName = args.siteName || context.defaultSiteName;
        if (!corpName) {
            throw new Error('Corporation name is required. Please set context or provide corpName parameter.');
        }
        return { corpName, siteName };
    }
  • server.js:814-816 (registration)
    MCP server request handler for ListToolsRequestSchema that returns the full list of tools, including 'get_site', effectively registering it for discovery.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
        return { tools };
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves details but does not specify if it's read-only, requires authentication, has rate limits, or what happens if parameters are omitted. This is a significant gap for a tool with potential context-dependent behavior.

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, efficient sentence with no wasted words. It is front-loaded with the core purpose, making it easy to parse quickly. Every part of the sentence contributes directly to understanding the tool's function.

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 lack of annotations and output schema, the description is incomplete. It does not explain what 'details' are returned, error conditions, or behavioral traits like context defaults. For a tool with two parameters and no structured output, more context is needed to guide effective use.

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?

The input schema has 100% description coverage, documenting both parameters and their default context usage. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. With high schema coverage, a baseline score of 3 is appropriate.

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 states the tool's purpose as 'Get details of a specific site', which is clear but vague. It specifies the verb ('Get') and resource ('site'), but does not differentiate from sibling tools like 'list_sites' or 'get_corp_overview', nor does it clarify what 'details' entail. This makes it minimally adequate but lacking specificity.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools such as 'list_sites' for broader listings or 'get_corp_overview' for corporation-level details, nor does it specify prerequisites or exclusions. This leaves usage context unclear.

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