Skip to main content
Glama
purpleax

Fastly NGWAF MCP Server

by purpleax

list_corps

Retrieve all corporations accessible to your authenticated account for managing web application security configurations in Fastly's Next-Gen WAF.

Instructions

List all corporations accessible to the authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:50-53 (handler)
    Core implementation of listing corporations via Fastly NGWAF API GET /corps endpoint.
    async listCorps() {
        const response = await this.api.get('/corps');
        return response.data;
    }
  • MCP CallToolRequestSchema handler dispatch for the 'list_corps' tool, invoking the client method.
    case 'list_corps':
        result = await client.listCorps();
        break;
  • Tool schema definition including name, description, and empty input schema for list_corps.
        name: 'list_corps',
        description: 'List all corporations accessible to the authenticated user',
        inputSchema: {
            type: 'object',
            properties: {},
        },
    },
  • server.js:814-816 (registration)
    Registration handler for ListToolsRequestSchema that returns the tools list including list_corps.
    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 mentions authentication ('authenticated user') but lacks details on permissions, rate limits, pagination, or return format. For a list operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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, clear sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word 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.

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema) and lack of annotations, the description is adequate as a basic overview but incomplete for operational use. It doesn't explain what 'corporations' entails in this context or how results are returned, which could hinder an agent's ability to use it effectively without trial and error.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The description appropriately focuses on the tool's purpose without redundant parameter information, earning a high baseline score for this dimension.

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

Purpose4/5

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

The description clearly states the verb ('List') and resource ('corporations') with scope ('accessible to the authenticated user'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_corp_overview' or 'list_sites', which might have overlapping or related functionality.

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. With siblings like 'get_corp_overview' and 'list_sites', there's no indication of differences in scope, format, or use cases, leaving the agent to guess based on tool names alone.

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