Skip to main content
Glama
mako10k

Web Proxy MCP Server

by mako10k

ssl_ca_status

Check SSL certificate authority status and configuration for proxy server security monitoring.

Instructions

Get current CA status and configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler case for 'ssl_ca_status' in _handleSSLTool method. Calls sslManager.getCAStatus() and returns formatted text response with JSON status.
    case 'ssl_ca_status':
      const status = this.sslManager.getCAStatus();
      return {
        content: [{
          type: "text",
          text: `🔒 SSL Manager Status\n\n${JSON.stringify(status, null, 2)}`
        }]
      };
  • Tool definition including name, description, and empty input schema (no parameters required). Used for MCP tool listing and validation.
    ssl_ca_status: {
      name: "ssl_ca_status",
      description: "Get current CA status and configuration",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • Core helper method that returns the SSL CA status object used by the tool handler.
    getCAStatus() {
      return {
        initialized: this.initialized,
        currentCA: this.currentCA,
        caDir: this.caDir,
        caInfo: this.caInfo || null
      };
    }
  • index.js:77-91 (registration)
    MCP server CallTool request handler that routes tool calls (including ssl_ca_status) to ToolHandlers.handleTool for execution.
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        const result = await this.toolHandlers.handleTool(name, args || {});
    
        if (result.isError) {
          throw new McpError(
            ErrorCode.InternalError,
            result.error
          );
        }
    
        return result;
  • index.js:66-74 (registration)
    MCP server ListTools request handler that registers all tools (including ssl_ca_status) from tool-definitions.js for discovery.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: Object.entries(TOOLS).map(([name, tool]) => ({
          name,
          description: tool.description,
          inputSchema: tool.inputSchema
        }))
      };
    });
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-only operation, it doesn't specify whether this requires special permissions, what format the status information returns in, or if there are any rate limits. The description lacks essential context about what 'CA status and configuration' actually includes.

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 perfectly concise - a single sentence that communicates the essential purpose without any wasted words. It's front-loaded with the core functionality and doesn't include 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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'CA status' means, what configuration details are returned, or what format the response takes. Given the complexity implied by 'CA status and configuration' and the lack of structured documentation, more descriptive context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't waste space discussing non-existent parameters, though it could theoretically mention that no parameters are required for this status check.

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 resource ('CA status and configuration'), making the tool's purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'ssl_list_cas' which might provide overlapping information about CAs, missing an opportunity for sibling differentiation.

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 'ssl_list_cas' or 'ssl_get_ca_certificate'. There's no mention of prerequisites, timing considerations, or what makes this tool the right choice for obtaining CA status versus other SSL-related 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/mako10k/mcp-web-proxy'

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