Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_get_test_result

Retrieve detailed security test results in JSON format for vulnerability analysis and assessment reporting.

Instructions

Get detailed test results in JSON format

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationTokenYesApplication token
resultTokenYesResult token from test start

Implementation Reference

  • The handler function 'getTestResult' that executes the 'beagle_get_test_result' tool logic.
    private async getTestResult(args: any) {
      const result = await this.makeRequest(
        `/test/result?application_token=${args.applicationToken}&result_token=${args.resultToken}`
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Test results:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • The definition and input schema registration for the 'beagle_get_test_result' tool.
    {
      name: "beagle_get_test_result",
      description: "Get detailed test results in JSON format",
      inputSchema: {
        type: "object",
        properties: {
          applicationToken: { type: "string", description: "Application token" },
          resultToken: { type: "string", description: "Result token from test start" },
        },
        required: ["applicationToken", "resultToken"],
      },
    },
  • src/index.ts:318-319 (registration)
    The request handler registration mapping 'beagle_get_test_result' to its corresponding implementation method.
    case "beagle_get_test_result":
      return await this.getTestResult(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 for behavioral disclosure. While 'Get' implies a read operation, it doesn't specify authentication requirements, rate limits, error conditions, or what constitutes 'detailed' results. The JSON format mention is helpful but insufficient for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just 7 words, front-loading the core purpose. However, it may be too brief given the lack of annotations and presence of similar sibling tools, potentially sacrificing necessary context for efficiency.

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?

For a tool with no annotations, no output schema, and multiple similar sibling tools, the description is insufficient. It doesn't explain what 'detailed test results' include, how they differ from test status, or provide any context about the testing system. The JSON format mention is the only helpful addition.

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?

With 100% schema description coverage, the schema already documents both parameters adequately. The description adds no additional parameter context beyond what's in the schema, so it meets the baseline expectation but doesn't provide extra value like explaining token relationships or format requirements.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Get detailed test results in JSON format', which clearly indicates a retrieval operation with a specific output format. However, it doesn't distinguish this from sibling tools like 'beagle_get_test_status' or 'beagle_list_test_sessions', leaving ambiguity about when to use each test-related get operation.

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 about when to use this tool versus alternatives. With multiple test-related sibling tools (get_test_status, list_test_sessions, list_running_tests), the description offers no context about prerequisites, timing, or differentiation from these similar tools.

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