Skip to main content
Glama
purpleax

Fastly NGWAF MCP Server

by purpleax

get_context

Retrieve current Fastly NGWAF context including corporation and site names to manage web application security configurations.

Instructions

Get the current context (corp and site names)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'get_context' tool within the CallToolRequestSchema switch statement. Returns the current default corporation and site names from the global context object.
    case 'get_context':
        result = {
            context: {
                defaultCorpName: context.defaultCorpName,
                defaultSiteName: context.defaultSiteName,
            },
        };
        break;
  • Schema definition for the 'get_context' tool, specifying no input parameters required.
        name: 'get_context',
        description: 'Get the current context (corp and site names)',
        inputSchema: {
            type: 'object',
            properties: {},
        },
    },
  • server.js:814-816 (registration)
    Registration of the ListToolsRequestSchema handler, which returns the tools array containing the 'get_context' tool definition.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
        return { tools };
    });
  • Global context object that persists the defaultCorpName and defaultSiteName values retrieved by the 'get_context' tool.
    let context = {};
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 states it 'Get[s] the current context' but doesn't explain what 'current context' means operationally, whether it's cached or fetched, if it requires authentication, or what happens if no context is set. This leaves key behavioral traits unspecified.

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 that directly states the tool's purpose without any wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimal. It lacks context on what 'current context' entails, how it's used, or what the return value includes, making it incomplete for guiding an agent effectively in a system with many sibling tools.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it implies the tool fetches context without inputs, aligning with the schema. Baseline is 4 for zero parameters.

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 'Get' and the resource 'current context (corp and site names)', making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'set_context' or 'discover_environment', which might also relate to context, so it doesn't fully distinguish itself.

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 doesn't mention prerequisites, such as whether context needs to be set first, or compare it to siblings like 'set_context' or 'get_corp_overview', leaving the agent without usage context.

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