Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_create_application

Create a new application for security testing in Beagle Security projects. Specify name, URL, project key, and type (WEB or API) to initiate security assessments.

Instructions

Create a new application in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesApplication name
urlYesApplication URL
projectKeyYesProject key
typeYesApplication type

Implementation Reference

  • The handler function 'createApplication' that performs the API call to create an application.
    private async createApplication(args: any) {
      const result = await this.makeRequest("/applications", {
        method: "POST",
        body: JSON.stringify({
          name: args.name,
          url: args.url,
          projectKey: args.projectKey,
          type: args.type,
        }),
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Application created successfully:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • Definition of the 'beagle_create_application' tool including its input schema.
    {
      name: "beagle_create_application",
      description: "Create a new application in a project",
      inputSchema: {
        type: "object",
        properties: {
          name: { type: "string", description: "Application name" },
          url: { type: "string", description: "Application URL" },
          projectKey: { type: "string", description: "Project key" },
          type: { type: "string", enum: ["WEB", "API"], description: "Application type" },
        },
        required: ["name", "url", "projectKey", "type"],
      },
    },
  • src/index.ts:294-295 (registration)
    Registration of the 'beagle_create_application' tool in the request handler switch statement.
    case "beagle_create_application":
      return await this.createApplication(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a creation operation, implying it's a write/mutation, but doesn't cover critical aspects like required permissions, whether the operation is idempotent, what happens on duplicate names, or typical response format. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, and there's no redundancy or fluff.

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 this is a mutation tool (creation) with no annotations and no output schema, the description is incomplete. It doesn't address behavioral traits like side effects, error conditions, or return values, which are crucial for an agent to use it correctly. The high schema coverage helps with inputs, but overall context for safe and effective invocation is lacking.

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 fully documents all four parameters (name, url, projectKey, type) with descriptions and enum values. The description adds no additional parameter semantics beyond implying these are needed for creation. This meets the baseline of 3, as the schema does the heavy lifting, but the description doesn't enhance understanding of parameter roles or constraints.

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 ('Create') and resource ('new application in a project'), making the purpose immediately understandable. It distinguishes from siblings like 'beagle_modify_application' (update) and 'beagle_delete_application' (remove), though it doesn't explicitly contrast with them. The description is specific but could be more precise about what constitutes an 'application' in this context.

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 (e.g., needing an existing project), exclusions, or comparisons to siblings like 'beagle_modify_application' for updates. The agent must infer usage from the tool name and context alone, which is insufficient for optimal selection.

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