Skip to main content
Glama
turbot
by turbot

steampipe_plugin_list

List all installed Steampipe plugins to see available data sources like AWS, GCP, or Azure for querying.

Instructions

List all Steampipe plugins installed on the system. Plugins provide access to different data sources like AWS, GCP, or Azure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that checks for database availability, executes a SQL query to list Steampipe plugins and versions from the steampipe_plugin table, returns JSON result or error.
    handler: async (db: DatabaseService) => {
      if (!db) {
        return {
          content: [{
            type: "text",
            text: "Database not available. Please ensure Steampipe is running and try again."
          }],
          isError: true
        };
      }
    
      try {
        const query = `
          SELECT 
            plugin,
            version
          FROM steampipe_plugin
          ORDER BY plugin
        `;
    
        const result = await db.executeQuery(query);
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify({ plugins: result })
          }]
        };
      } catch (err) {
        logger.error("Error listing plugins:", err);
        return {
          content: [{
            type: "text",
            text: `Failed to list plugins: ${err instanceof Error ? err.message : String(err)}`
          }],
          isError: true
        };
      }
    }
  • Input schema defining no required properties for the tool.
    inputSchema: {
      type: "object",
      properties: {},
      additionalProperties: false
    },
  • The steampipe_plugin_list tool is registered in the central tools export object used by the MCP server.
    export const tools = {
      steampipe_query: queryTool as DbTool,
      steampipe_table_list: tableListTool as DbTool,
      steampipe_table_show: tableShowTool as DbTool,
      steampipe_plugin_list: pluginListTool as DbTool,
      steampipe_plugin_show: pluginShowTool as DbTool,
    } as const;
  • Import statement for the steampipe_plugin_list tool implementation.
    import { tool as pluginListTool } from './steampipe_plugin_list.js';
Behavior3/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 describes what the tool does (lists plugins) and provides useful context about plugins providing access to data sources, but doesn't disclose behavioral traits like whether this requires specific permissions, how results are formatted, or if there are any rate limits. It adds some value but lacks operational details.

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?

Two concise sentences with zero waste. First sentence states the core purpose, second adds helpful context about plugins. Well-structured and front-loaded with the essential information.

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 no annotations, no output schema, and moderate complexity (listing operation), the description is adequate but incomplete. It explains what the tool does and provides context about plugins, but lacks details about return format, error conditions, or operational constraints that would be helpful for an agent.

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 with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose. Baseline for 0 parameters is 4, as it avoids unnecessary parameter discussion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('List all') and resource ('Steampipe plugins installed on the system'), with additional context about what plugins provide. It distinguishes from siblings like steampipe_plugin_show (detail view) and steampipe_table_list (different resource type).

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 when needing to see installed plugins, but doesn't explicitly state when to use this vs. alternatives like steampipe_plugin_show for detailed plugin information or steampipe_table_list for table listings. No explicit exclusions or prerequisites are mentioned.

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/turbot/steampipe-mcp'

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