Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_list_projects

Retrieve all security testing projects and applications from the Beagle Security platform to monitor assessments and manage security workflows.

Instructions

List all projects and applications

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeTeamNoInclude team projects

Implementation Reference

  • The implementation of the `listProjects` handler.
    private async listProjects(args: any) {
      const endpoint = args.includeTeam 
        ? "/projects?include_team=true" 
        : "/projects";
      
      const result = await this.makeRequest(endpoint);
    
      return {
        content: [
          {
            type: "text",
            text: `Projects:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • src/index.ts:82-88 (registration)
    Tool registration for beagle_list_projects.
    name: "beagle_list_projects",
    description: "List all projects and applications",
    inputSchema: {
      type: "object",
      properties: {
        includeTeam: { type: "boolean", description: "Include team projects" },
      },
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention permissions, rate limits, pagination, or output format, leaving critical operational details unspecified for a list 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, efficient sentence with no wasted words. It is appropriately sized and front-loaded, clearly stating the core functionality without unnecessary elaboration.

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, no output schema, and a list operation that likely returns structured data, the description is incomplete. It fails to explain what information is returned, how results are formatted, or any limitations, leaving significant gaps for agent usage.

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 input schema fully documents the single parameter. The description adds no parameter-specific information beyond what the schema provides, meeting the baseline for high 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 action ('List') and resources ('projects and applications'), making the purpose understandable. However, it doesn't differentiate from sibling 'beagle_list_applications', which appears to be a more specific version, leaving some ambiguity about scope.

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_list_applications' or other list tools. The description lacks context about prerequisites, timing, or exclusions, offering minimal usage direction.

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