Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_stop_test

Stop a running security test in Beagle Security by providing the application token to halt ongoing assessments.

Instructions

Stop a running test

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationTokenYesApplication token

Implementation Reference

  • The `stopTest` function handles the implementation of the `beagle_stop_test` tool, making a POST request to `/test/stop` with the application token.
    private async stopTest(args: any) {
      const result = await this.makeRequest("/test/stop", {
        method: "POST",
        body: JSON.stringify({
          applicationToken: args.applicationToken,
        }),
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Test stopped:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • src/index.ts:229-230 (registration)
    Registration of the `beagle_stop_test` tool definition.
    name: "beagle_stop_test",
    description: "Stop a running test",
  • Input schema for the `beagle_stop_test` tool.
    inputSchema: {
      type: "object",
      properties: {
        applicationToken: { type: "string", description: "Application token" },
      },
      required: ["applicationToken"],
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Stop' implies a mutation/control action, it doesn't specify whether this is destructive (does it delete test data?), what permissions are required, or what happens after stopping (does it return status?). The description is minimal and lacks critical behavioral context for a control operation.

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 at just three words, with zero wasted language. It's front-loaded with the core action and target, making it immediately understandable despite its brevity.

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 mutation/control tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'stopping' entails behaviorally, what the expected outcome is, or how this interacts with other tools in the system (particularly 'beagle_start_test' and 'beagle_list_running_tests'). The minimal description leaves too many questions unanswered.

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 fully documents the single parameter 'applicationToken'. The description adds no additional parameter information beyond what's in the schema, meeting the baseline for high schema coverage but not providing extra value.

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 ('Stop') and the target ('a running test'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from its sibling 'beagle_start_test' beyond the obvious verb difference, missing an opportunity to clarify their complementary relationship.

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 a test to be running), nor does it reference the sibling 'beagle_list_running_tests' which would logically be used first to identify tests to stop.

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