Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_list_applications

Retrieve all applications within a specified Beagle Security project to manage and monitor security testing assets.

Instructions

List all applications under a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectKeyYesProject key

Implementation Reference

  • The handler function 'listApplications' that performs the API request to fetch applications for a given project key.
    private async listApplications(args: any) {
      const result = await this.makeRequest(`/applications?project_key=${args.projectKey}`);
    
      return {
        content: [
          {
            type: "text",
            text: `Applications:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • Schema definition for 'beagle_list_applications' describing the tool input.
      name: "beagle_list_applications",
      description: "List all applications under a project",
      inputSchema: {
        type: "object",
        properties: {
          projectKey: { type: "string", description: "Project key" },
        },
        required: ["projectKey"],
      },
    },
  • src/index.ts:300-301 (registration)
    Tool registration where the 'beagle_list_applications' request is routed to the corresponding handler.
    case "beagle_list_applications":
      return await this.listApplications(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 basic action without disclosing behavioral traits such as pagination, rate limits, permissions required, or what 'all applications' entails (e.g., includes deleted ones?). This leaves significant gaps for a tool that likely returns a list.

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 with zero waste, front-loading the core action and resource. It's appropriately sized for a simple list operation.

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 no annotations and no output schema, the description is incomplete for a tool that likely returns a list of applications. It doesn't explain return values, error conditions, or behavioral details, leaving the agent with insufficient context for reliable 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 description implies the 'projectKey' parameter is needed to scope the listing, but the schema already has 100% coverage with a clear description ('Project key'). No additional semantics, like format examples or constraints, are provided beyond what the schema offers.

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 ('List') and resource ('applications under a project'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'beagle_list_projects' or 'beagle_list_test_sessions' beyond the resource type, missing explicit sibling distinction.

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 like 'beagle_get_application' for single applications or 'beagle_list_projects' for listing projects. The description lacks context on prerequisites, filtering options, or exclusions.

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