Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_delete_application

Remove an application from the Beagle Security platform to manage security testing projects and assessments.

Instructions

Delete an application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationTokenYesApplication token

Implementation Reference

  • Handler function for beagle_delete_application which makes a DELETE request to the API.
    private async deleteApplication(args: any) {
      const result = await this.makeRequest(`/applications?application_token=${args.applicationToken}`, {
        method: "DELETE",
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Application deleted:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • Definition of the beagle_delete_application tool, including input schema.
    {
      name: "beagle_delete_application",
      description: "Delete an application",
      inputSchema: {
        type: "object",
        properties: {
          applicationToken: { type: "string", description: "Application token" },
        },
        required: ["applicationToken"],
      },
    },
  • src/index.ts:302-303 (registration)
    Registration of beagle_delete_application in the request handler switch statement.
    case "beagle_delete_application":
      return await this.deleteApplication(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. It states 'Delete' implying a destructive mutation, but doesn't specify if deletion is permanent, reversible, requires specific permissions, or has side effects (e.g., cascading deletions). This leaves critical behavioral traits undocumented for a destructive 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 a single, direct sentence with zero waste. It is front-loaded and efficiently conveys the core action without unnecessary words, 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?

For a destructive tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permanence or permissions, nor does it explain the outcome (e.g., success confirmation or error handling). Given the complexity of deletion operations, more context is needed for safe 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 input schema has 100% description coverage, with the parameter 'applicationToken' clearly documented. The description adds no additional meaning beyond the schema, such as explaining what an application token is or where to find it. Baseline 3 is appropriate since 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 ('Delete') and resource ('an application'), making the purpose immediately understandable. It distinguishes from siblings like 'beagle_get_application' or 'beagle_modify_application' by specifying deletion. However, it doesn't specify what type of application (e.g., Beagle application) or provide additional context about the resource.

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. It doesn't mention prerequisites (e.g., needing an existing application token), exclusions, or comparisons with siblings like 'beagle_delete_project' for related operations. The description lacks context for decision-making.

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