Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_start_test

Initiate automated penetration testing to identify security vulnerabilities in web applications using Beagle Security's assessment capabilities.

Instructions

Start an automated penetration test

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationTokenYesApplication token

Implementation Reference

  • The 'startTest' method handles the 'beagle_start_test' tool call by making a POST request to the Beagle Security API.
    private async startTest(args: any) {
      const result = await this.makeRequest("/test/start", {
        method: "POST",
        body: JSON.stringify({
          applicationToken: args.applicationToken,
        }),
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Test started:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • The tool schema registration for 'beagle_start_test', defining the input requirements.
    {
      name: "beagle_start_test",
      description: "Start an automated penetration test",
      inputSchema: {
        type: "object",
        properties: {
          applicationToken: { type: "string", description: "Application token" },
        },
        required: ["applicationToken"],
      },
    },
  • src/index.ts:312-313 (registration)
    The tool handler switch case in 'setupToolHandlers' that routes the 'beagle_start_test' request to the 'startTest' implementation.
    case "beagle_start_test":
      return await this.startTest(args);
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. While 'Start' implies a write/mutation operation, it doesn't disclose what permissions are needed, whether this is idempotent, what happens if a test is already running, rate limits, or what the expected outcome is. The description is too minimal for a tool that initiates potentially resource-intensive operations.

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 extremely concise - a single sentence with no wasted words. It's front-loaded with the core action and resource. While it may be too minimal for completeness, it earns full marks for 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?

For a tool that initiates automated penetration tests (a complex, potentially destructive operation) with no annotations and no output schema, the description is inadequate. It doesn't explain what 'starting a test' entails, what gets initiated, expected duration, or what the user should do next. Given the context of security testing tools, more behavioral context is needed.

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%, so the schema already documents the single 'applicationToken' parameter. The description adds no additional parameter context beyond what's in the schema. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 action ('Start') and the resource ('an automated penetration test'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'beagle_stop_test' or 'beagle_get_test_status' beyond the obvious action difference.

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 (like needing an existing application/project), what happens after starting a test, or when to use 'beagle_stop_test' or 'beagle_get_test_status' instead.

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/beaglesecurity/beagle-security-mcp-server'

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