Skip to main content
Glama

db_hosts

List all hosts in a Metasploit workspace to manage penetration testing targets and organize network reconnaissance data.

Instructions

List all hosts in the current workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceNoOptional: workspace name to query

Implementation Reference

  • Handler for the 'db_hosts' tool: executes Metasploit 'hosts' command (optionally after switching workspace) via executeMsfCommand and returns formatted JSON response.
    case "db_hosts": {
      const { workspace } = args as { workspace?: string };
      const commands = workspace 
        ? [`workspace ${workspace}`, `hosts`]
        : [`hosts`];
    
      try {
        const hosts = await executeMsfCommand(commands);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  success: true,
                  workspace: workspace || "default",
                  hosts,
                },
                null,
                2
              ),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: false,
                error: error.message,
              }),
            },
          ],
        };
      }
    }
  • Input schema for 'db_hosts' tool defining optional 'workspace' parameter.
    inputSchema: {
      type: "object",
      properties: {
        workspace: {
          type: "string",
          description: "Optional: workspace name to query",
        },
      },
    },
  • src/index.ts:153-165 (registration)
    Registration of the 'db_hosts' tool in the MCP tools array, including name, description, and input schema.
    {
      name: "db_hosts",
      description: "List all hosts in the current workspace",
      inputSchema: {
        type: "object",
        properties: {
          workspace: {
            type: "string",
            description: "Optional: workspace name to query",
          },
        },
      },
    },
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. It states this is a list operation, implying it's read-only and non-destructive, but doesn't mention any constraints like permissions, rate limits, or what 'hosts' entails (e.g., IP addresses, names). It adds little beyond the basic action.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 (1 optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic action but lacks details on usage context, behavioral traits, or output format, leaving gaps that could hinder an agent's understanding.

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 schema description coverage is 100%, so the schema already documents the single optional 'workspace' parameter. The description adds minimal value by implying a default 'current workspace', but doesn't clarify semantics like format or precedence. Baseline 3 is appropriate as the schema does most of the work.

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 ('List all hosts') and resource ('in the current workspace'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'db_services' or 'db_workspaces' that might also list workspace-related data, 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 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 'db_services' or 'nmap_scan'. It mentions 'current workspace' but doesn't explain if this is the default or how it relates to the optional workspace parameter, offering minimal context.

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/andreransom58-coder/kali-metasploit-mcp'

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