Skip to main content
Glama

validate_all_security

Run comprehensive website security tests using Mozilla Observatory and SSL Labs to assess vulnerabilities and SSL configuration.

Instructions

Run all security tests (Mozilla Observatory + SSL Labs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
emailYesEmail for SSL Labs
waitForSSLNoWait for SSL Labs to complete

Implementation Reference

  • Core handler function implementing the 'validate_all_security' tool logic. Orchestrates Mozilla Observatory and SSL Labs security analyses, combines results with summary.
    export async function runAllSecurity(
      url: string,
      options: SecurityTestOptions
    ): Promise<AllSecurityResult> {
      // Run both security tools
      const mozillaResult = await analyzeMozillaObservatory(url);
      const sslResult = options.sslLabs.waitForComplete
        ? await analyzeSSLLabsComplete(url, options.sslLabs)
        : await analyzeSSLLabs(url, options.sslLabs);
    
      return {
        url,
        timestamp: new Date().toISOString(),
        mozilla_observatory: mozillaResult,
        ssl_labs: sslResult,
        summary: {
          mozilla_grade: mozillaResult.grade,
          ssl_grade: sslResult.grade,
          overall_success: mozillaResult.success && (sslResult.success || sslResult.status !== 'ERROR'),
        },
      };
    }
  • index.ts:271-283 (registration)
    MCP tool registration for 'validate_all_security', including name, description, and input schema.
    {
      name: 'validate_all_security',
      description: 'Run all security tests (Mozilla Observatory + SSL Labs).',
      inputSchema: {
        type: 'object',
        properties: {
          url: { type: 'string' },
          email: { type: 'string', description: 'Email for SSL Labs' },
          waitForSSL: { type: 'boolean', description: 'Wait for SSL Labs to complete' },
        },
        required: ['url', 'email'],
      },
    },
  • Zod schema for validating inputs to the validate_all_security tool.
    const AllSecurityArgsSchema = z.object({
      url: z.string().url(),
      email: z.string().email(),
      waitForSSL: z.boolean().optional(),
    });
  • Tool dispatcher case in the main CallToolRequestHandler that validates arguments and invokes runAllSecurity for 'validate_all_security'.
    case 'validate_all_security': {
      const validatedArgs = AllSecurityArgsSchema.parse(args);
      const result = await runAllSecurity(validatedArgs.url, {
        sslLabs: {
          email: validatedArgs.email,
          waitForComplete: validatedArgs.waitForSSL,
        },
      });
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • TypeScript interface defining the output structure of the validate_all_security tool.
    export interface AllSecurityResult {
      url: string;
      timestamp: string;
      mozilla_observatory: MozillaObservatoryResult;
      ssl_labs: SSLLabsResult;
      summary: {
        mozilla_grade: string;
        ssl_grade?: string;
        overall_success: boolean;
      };
    }
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 mentions running tests but lacks details on behavioral traits such as execution time, rate limits, authentication needs, or what happens during 'waitForSSL'. This is inadequate for a tool with parameters and no output schema.

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 zero waste. It is front-loaded and appropriately sized, making it easy to parse without unnecessary details.

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, no output schema, and incomplete parameter documentation, the description is insufficient. It does not cover return values, error handling, or tool behavior, leaving significant gaps for a security testing tool with multiple parameters.

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 67% (2 out of 3 parameters have descriptions). The description does not add meaning beyond the schema, as it does not explain parameter roles or interactions. With moderate schema coverage, the baseline is 3, but it fails to compensate for the undocumented 'url' parameter.

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 'Run' and the resource 'all security tests', specifying which tests (Mozilla Observatory + SSL Labs). It distinguishes from sibling tools like 'validate_security_mozilla_observatory' and 'validate_security_ssl_labs' by indicating it runs both, but could be more specific about scope or integration.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for security testing, but does not explicitly state when to use this tool versus alternatives like individual security tools or the comprehensive 'validate_comprehensive'. No guidance on prerequisites or exclusions is provided, leaving context inferred.

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/cordlesssteve/webby-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server