Skip to main content
Glama

Verify Wire Encryption

verify-wire-encryption

Check if your Firebird database connection uses wire encryption to protect data in transit. This tool verifies encryption status for secure communication.

Instructions

Verifies if the current database connection is using wire encryption (requires native driver).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'verify-wire-encryption' checks environment variables (USE_NATIVE_DRIVER, WIRE_CRYPT) to determine if the database connection uses wire encryption and returns status information with recommendations.
    handler: async () => {
        logger.info("Verifying wire encryption status");
    
        try {
            // Check if native driver is available
            const driverInfo = {
                hasNativeDriver: process.env.USE_NATIVE_DRIVER === 'true',
                wireEncryptionEnabled: process.env.WIRE_CRYPT === 'Enabled',
                driverType: process.env.USE_NATIVE_DRIVER === 'true' ? 'native' : 'pure-js',
                recommendation: process.env.USE_NATIVE_DRIVER !== 'true'
                    ? 'Wire encryption requires the native driver. Set USE_NATIVE_DRIVER=true and install node-firebird-driver-native.'
                    : 'Native driver is configured. Ensure WIRE_CRYPT=Enabled for encryption.'
            };
    
            return {
                content: [{
                    type: "text",
                    text: formatForClaude(driverInfo)
                }]
            };
        } catch (error) {
            const errorResponse = wrapError(error);
            logger.error(`Error verifying wire encryption: ${errorResponse.error}`);
    
            return {
                content: [{
                    type: "text",
                    text: formatForClaude(errorResponse)
                }]
            };
        }
    }
  • Zod input schema for the verify-wire-encryption tool, which takes no arguments.
    export const VerifyWireEncryptionArgsSchema = z.object({});
  • Registration of the 'verify-wire-encryption' tool within the setupDatabaseTools function, adding it to the tools Map.
    tools.set("verify-wire-encryption", {
        name: "verify-wire-encryption",
        title: "Verify Wire Encryption",
        description: "Verifies if the current database connection is using wire encryption (requires native driver).",
        inputSchema: VerifyWireEncryptionArgsSchema,
        handler: async () => {
            logger.info("Verifying wire encryption status");
    
            try {
                // Check if native driver is available
                const driverInfo = {
                    hasNativeDriver: process.env.USE_NATIVE_DRIVER === 'true',
                    wireEncryptionEnabled: process.env.WIRE_CRYPT === 'Enabled',
                    driverType: process.env.USE_NATIVE_DRIVER === 'true' ? 'native' : 'pure-js',
                    recommendation: process.env.USE_NATIVE_DRIVER !== 'true'
                        ? 'Wire encryption requires the native driver. Set USE_NATIVE_DRIVER=true and install node-firebird-driver-native.'
                        : 'Native driver is configured. Ensure WIRE_CRYPT=Enabled for encryption.'
                };
    
                return {
                    content: [{
                        type: "text",
                        text: formatForClaude(driverInfo)
                    }]
                };
            } catch (error) {
                const errorResponse = wrapError(error);
                logger.error(`Error verifying wire encryption: ${errorResponse.error}`);
    
                return {
                    content: [{
                        type: "text",
                        text: formatForClaude(errorResponse)
                    }]
                };
            }
        }
    });
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses a behavioral trait ('requires native driver'), which is useful context beyond basic functionality. However, it doesn't cover other aspects like whether this is a read-only operation, potential side effects, or error handling, leaving gaps in behavioral transparency.

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 that front-loads the core purpose and includes a key constraint. There is no wasted text, and every part earns its place by providing essential information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (0 parameters, no output schema), the description is adequate but minimal. It covers the purpose and a constraint, but for a verification tool with no annotations, it could benefit from more context (e.g., what 'wire encryption' means, typical use cases, or result interpretation) to be fully complete.

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 0 parameters, and the schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for this scenario is 4, as the description appropriately doesn't add unnecessary param info, but it could slightly elaborate on context (e.g., what 'wire encryption' entails) to reach a perfect score.

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 'verifies' and the resource 'wire encryption on current database connection', making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its siblings (like 'get-database-info' or 'system-health-check'), which might also provide encryption status information, so it doesn't reach the highest score.

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 includes 'requires native driver', which implies a prerequisite context for usage, but it doesn't specify when to use this tool versus alternatives (e.g., 'get-database-info' for broader info or other verification tools). This provides some implied guidance but lacks explicit comparisons or exclusions.

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/PuroDelphi/mcpFirebird'

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