Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_list_test_sessions

Retrieve all security test sessions for an application to monitor and manage penetration testing assessments.

Instructions

List all test sessions for an application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationTokenYesApplication token
countNoNumber of sessions to retrieve

Implementation Reference

  • The handler method `listTestSessions` that executes the logic to retrieve test sessions by making an API request.
    private async listTestSessions(args: any) {
      const endpoint = args.count 
        ? `/test/sessions?application_token=${args.applicationToken}&count=${args.count}`
        : `/test/sessions?application_token=${args.applicationToken}`;
      
      const result = await this.makeRequest(endpoint);
    
      return {
        content: [
          {
            type: "text",
            text: `Test sessions:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
  • Definition of the `beagle_list_test_sessions` tool including its input schema.
    name: "beagle_list_test_sessions",
    description: "List all test sessions for an application",
    inputSchema: {
      type: "object",
      properties: {
        applicationToken: { type: "string", description: "Application token" },
        count: { type: "number", description: "Number of sessions to retrieve" },
      },
      required: ["applicationToken"],
    },
  • src/index.ts:320-321 (registration)
    Registration of the `beagle_list_test_sessions` tool in the request handler switch statement.
    case "beagle_list_test_sessions":
      return await this.listTestSessions(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 it's a list operation. It doesn't disclose behavioral traits such as pagination, rate limits, authentication needs, or what 'all' entails (e.g., historical vs. active sessions). This leaves significant gaps for a tool with potential complexity.

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, direct sentence with zero waste. It is appropriately sized and front-loaded, clearly stating the tool's purpose 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 and no output schema, the description is incomplete. It lacks details on return values, error conditions, or behavioral constraints. For a list operation that might involve pagination or filtering, this leaves the agent with insufficient context to use the tool effectively.

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 already documents both parameters ('applicationToken' and 'count'). The description adds no additional meaning beyond implying filtering by application, which is covered by the required parameter. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 ('test sessions for an application'), making the purpose understandable. It distinguishes from siblings like 'beagle_list_applications' or 'beagle_list_projects' by specifying test sessions, but doesn't explicitly contrast with 'beagle_list_running_tests' which might overlap in 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_running_tests' or 'beagle_get_test_status'. The description implies usage for listing all test sessions, but lacks context on prerequisites, timing, 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