Skip to main content
Glama
beaglesecurity

Beagle Security MCP Server

Official

beagle_get_domain_signature

Retrieve domain verification signatures for security testing applications using an application token to authenticate and validate domains.

Instructions

Get domain verification signature

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applicationTokenYesApplication token

Implementation Reference

  • The handler implementation for the beagle_get_domain_signature tool.
    private async getDomainSignature(args: any) {
      const result = await this.makeRequest(`/applications/signature?application_token=${args.applicationToken}`);
    
      return {
        content: [
          {
            type: "text",
            text: `Domain verification signature:\n${JSON.stringify(result, null, 2)}`,
          },
        ],
      };
    }
  • Registration and input schema definition for the beagle_get_domain_signature tool.
      name: "beagle_get_domain_signature",
      description: "Get domain verification signature",
      inputSchema: {
        type: "object",
        properties: {
          applicationToken: { type: "string", description: "Application token" },
        },
        required: ["applicationToken"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get' implies a read operation, but doesn't specify if this requires authentication, has rate limits, returns structured data, or involves side effects. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by conveying essential information without redundancy.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what a domain verification signature is, why it's needed, or what the return value looks like. For a tool with no structured behavioral data, the description should provide more context to be fully helpful.

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?

The input schema has 100% description coverage, with the single parameter 'applicationToken' documented as 'Application token'. The description adds no additional meaning beyond this, such as explaining what an application token is or how it relates to domain verification. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Get domain verification signature' clearly states the action (get) and the resource (domain verification signature), making the purpose understandable. However, it doesn't differentiate this tool from its sibling 'beagle_verify_domain', which appears related to domain verification, leaving some ambiguity about when to use each tool.

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?

The description provides no guidance on when to use this tool versus alternatives like 'beagle_verify_domain' or other domain-related operations. It lacks context about prerequisites, such as whether domain verification must be set up first, or when this signature is needed in the workflow.

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