Skip to main content
Glama
purpleax

Fastly NGWAF MCP Server

by purpleax

get_corp_overview

Retrieve attack overview data for a corporation using Fastly's Next-Gen WAF, including security incidents within specified date ranges.

Instructions

Get attack overview for a corporation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
corpNameNoCorporation name (uses context default if not provided)
fromNoStart date (e.g., "-7d")
untilNoEnd date (e.g., "-1d")

Implementation Reference

  • server.js:58-66 (handler)
    Core handler implementing the get_corp_overview tool logic. Fetches attack reports overview for a corporation from the Fastly NGWAF API, optionally filtered by date range.
    async getCorpOverview(corpName, from, until) {
        const params = new URLSearchParams();
        if (from)
            params.append('from', from);
        if (until)
            params.append('until', until);
        const response = await this.api.get(`/corps/${corpName}/reports/attacks?${params.toString()}`);
        return response.data;
    }
  • Input schema definition for the get_corp_overview tool, defining parameters corpName, from, and until.
    inputSchema: {
        type: 'object',
        properties: {
            corpName: { type: 'string', description: 'Corporation name (uses context default if not provided)' },
            from: { type: 'string', description: 'Start date (e.g., "-7d")' },
            until: { type: 'string', description: 'End date (e.g., "-1d")' },
        },
    },
  • server.js:456-466 (registration)
    Tool registration in the tools array returned by listTools handler.
        name: 'get_corp_overview',
        description: 'Get attack overview for a corporation',
        inputSchema: {
            type: 'object',
            properties: {
                corpName: { type: 'string', description: 'Corporation name (uses context default if not provided)' },
                from: { type: 'string', description: 'Start date (e.g., "-7d")' },
                until: { type: 'string', description: 'End date (e.g., "-1d")' },
            },
        },
    },
  • server.js:900-903 (registration)
    MCP CallToolRequest handler case that invokes the get_corp_overview tool implementation using resolved context.
    case 'get_corp_overview':
        const { corpName: corpForOverview } = resolveContext(typedArgs);
        result = await client.getCorpOverview(corpForOverview, typedArgs.from, typedArgs.until);
        break;
  • Helper function resolveContext used to determine corpName from args or context, required for get_corp_overview.
    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 };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Get'), but doesn't specify permissions, rate limits, data freshness, or output format. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, straightforward sentence that efficiently conveys the core function without unnecessary words. It is front-loaded with the main action, making it easy to parse, though it could be slightly more informative without losing conciseness.

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 insufficient for a tool that likely returns complex attack data. It doesn't explain what an 'attack overview' includes, how results are structured, or any behavioral traits like error handling, leaving the agent with incomplete context for 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 schema description coverage is 100%, with clear descriptions for all three parameters (corpName, from, until). The description adds no additional semantic context beyond the schema, such as explaining what 'attack overview' entails or how parameters interact, so it meets the baseline for adequate but unenriched parameter documentation.

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 action ('Get attack overview') and target ('for a corporation'), which clarifies the tool's purpose. However, it doesn't differentiate from sibling tools like 'get_analytics' or 'get_context' that might also provide overviews, and 'attack overview' remains somewhat vague without specifying what metrics or data it includes.

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 such as 'get_analytics' or 'list_events', nor are there any prerequisites or exclusions mentioned. The description only states what it does, without context for its application relative to other tools.

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