Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_get_application

Retrieve security testing application details using an application token to access project information and assessment data.

Instructions

Get application details by token

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationTokenYesApplication token

Implementation Reference

  • The implementation of the getApplication handler, which fetches application details by token via a network request.
    private async getApplication(args: any) {
      const result = await this.makeRequest(`/applications?application_token=${args.applicationToken}`);
    
      return {
        content: [
          {
            type: "text",
            text: `Application details:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • The definition of the beagle_get_application tool in the MCP tools list, including its schema and name.
      name: "beagle_get_application",
      description: "Get application details by token",
      inputSchema: {
        type: "object",
        properties: {
          applicationToken: { type: "string", description: "Application token" },
        },
        required: ["applicationToken"],
      },
    },
  • src/index.ts:296-297 (registration)
    The request handler routing where beagle_get_application is mapped to the getApplication method.
    case "beagle_get_application":
      return await this.getApplication(args);
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 a read operation ('Get'), implying non-destructive behavior, but doesn't disclose error handling, authentication needs, rate limits, or response format. For a tool with no annotation coverage, this is a significant gap in behavioral context.

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 and front-loaded with a single, clear sentence. Every word earns its place, with no redundancy or fluff, making it easy for an agent 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. It doesn't explain what 'details' include, error behaviors, or response structure. For a tool that likely returns application data, more context is needed to guide the agent 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%, with the single parameter 'applicationToken' documented in the schema. The description adds minimal value by implying the token is used to retrieve details, but doesn't provide additional context like token format or examples. Baseline 3 is appropriate as the schema handles parameter documentation.

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 ('Get') and target ('application details'), and specifies the lookup method ('by token'). It distinguishes from siblings like 'beagle_list_applications' (which lists multiple) and 'beagle_modify_application' (which updates). However, it doesn't specify what 'details' include, leaving some ambiguity.

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 explicit guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid token) or contrast with siblings like 'beagle_list_applications' for browsing. The description implies usage when you have a token, but lacks context on error cases or alternatives.

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