Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_list_running_tests

Monitor active security assessments by retrieving a list of currently running penetration tests for users or teams.

Instructions

List all running tests for user or team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdNoTeam ID (optional, for team tests)

Implementation Reference

  • Handler method for listing running tests.
    private async listRunningTests(args: any) {
      const endpoint = args.teamId 
        ? `/test/runningsessions?teamid=${args.teamId}`
        : "/test/runningsessions";
      
      const result = await this.makeRequest(endpoint);
    
      return {
        content: [
          {
            type: "text",
            text: `Running tests:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • src/index.ts:264-272 (registration)
    Tool registration for beagle_list_running_tests.
      name: "beagle_list_running_tests",
      description: "List all running tests for user or team",
      inputSchema: {
        type: "object",
        properties: {
          teamId: { type: "string", description: "Team ID (optional, for team tests)" },
        },
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it's a list operation, implying read-only, but doesn't disclose behavioral traits like pagination, rate limits, authentication requirements, or what 'running' means (e.g., active vs. pending). The description is minimal and lacks context beyond the basic action.

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?

Extremely concise with a single, front-loaded sentence that directly states the tool's purpose. No wasted words or redundant information, 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 no annotations and no output schema, the description is incomplete for a tool that likely returns a list of tests. It doesn't explain return values (e.g., format, fields), error conditions, or behavioral aspects like real-time updates. For a list operation with potential complexity, this leaves significant gaps.

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%, with teamId documented as optional for team tests. The description adds marginal value by implying the parameter's purpose ('for user or team'), but doesn't provide syntax, format details, or examples beyond what the schema already states. Baseline 3 is appropriate given 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 ('List') and resource ('running tests'), with scope ('for user or team'). It distinguishes from siblings like beagle_list_test_sessions (which lists sessions, not running tests) and beagle_get_test_status (which gets status of a specific test). However, it doesn't explicitly differentiate from beagle_get_test_result, which could be ambiguous.

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 on when to use this tool versus alternatives. It doesn't specify prerequisites (e.g., authentication needs), when to use teamId vs. user context, or how it differs from beagle_list_test_sessions. The description implies usage but lacks explicit context 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