Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_create_project

Create a new security testing project in Beagle Security to initiate automated penetration tests and vulnerability assessments.

Instructions

Create a new project in Beagle Security

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
descriptionNoProject description
teamIdNoTeam ID (optional)

Implementation Reference

  • The createProject method handles the logic for the beagle_create_project tool.
    private async createProject(args: any) {
      const endpoint = args.teamId 
        ? `/projects?teamId=${args.teamId}`
        : "/projects";
      
      const result = await this.makeRequest(endpoint, {
        method: "POST",
        body: JSON.stringify({
          name: args.name,
          description: args.description,
        }),
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Project created successfully:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • The tool definition and input schema for beagle_create_project.
    {
      name: "beagle_create_project",
      description: "Create a new project in Beagle Security",
      inputSchema: {
        type: "object",
        properties: {
          name: { type: "string", description: "Project name" },
          description: { type: "string", description: "Project description" },
          teamId: { type: "string", description: "Team ID (optional)" },
        },
        required: ["name"],
      },
    },
  • src/index.ts:284-285 (registration)
    The tool handler registration in the switch statement for beagle_create_project.
    case "beagle_create_project":
      return await this.createProject(args);
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose permissions required, whether the operation is idempotent, rate limits, or what happens on success/failure. For a creation tool with zero annotation coverage, this is a significant gap in transparency.

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 appropriately sized and front-loaded, 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 complexity (a creation operation with no annotations and no output schema), the description is incomplete. It lacks information on behavioral traits, usage context, and expected outcomes, which are critical for an agent to invoke it correctly in a real-world scenario.

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 three parameters (name, description, teamId). The description adds no additional parameter semantics beyond what's in the schema, such as format constraints or examples, resulting in the baseline score for high schema coverage.

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 ('Create') and resource ('new project in Beagle Security'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'beagle_modify_project' or explain what distinguishes creating a project from creating an application ('beagle_create_application'), which prevents a perfect score.

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., authentication needs), when not to use it, or how it relates to sibling tools like 'beagle_modify_project' or 'beagle_create_application', leaving the agent with no context for 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