Skip to main content
Glama

list_plugins

Discover available plugins and their versions in the Android MCP Server to manage app control, UI automation, and device analysis capabilities.

Instructions

List all loaded MCP server plugins and their versions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `list_plugins` tool is registered and implemented directly within `registerPluginTools` in `src/mcp/plugin-loader.ts`. The handler logic is provided as the async function callback to `server.registerTool`.
    export function registerPluginTools(server: McpServer): void {
      server.registerTool(
        'list_plugins',
        {
          description: 'List all loaded MCP server plugins and their versions.',
          inputSchema: {},
        },
        async () => {
          return {
            content: [{
              type: 'text' as const,
              text: JSON.stringify({
                success: true,
                plugins: loadedPlugins.map(p => ({
                  name: p.name,
                  version: p.version,
                  description: p.description,
                })),
                totalLoaded: loadedPlugins.length,
              }, null, 2),
            }],
          };
        }
      );
    }
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 of behavioral disclosure. It minimally indicates the tool returns version information and filters for 'loaded' plugins, but lacks details on output format, pagination, or whether this triggers any server-side state changes.

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 action verb. Every element serves a purpose: 'List' (action), 'all loaded' (scope filter), 'MCP server plugins' (resource), and 'their versions' (specific data points returned).

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

Completeness4/5

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

Given the low complexity (zero parameters, simple listing operation) and absence of an output schema, the description is sufficiently complete to enable tool selection. However, it could have briefly indicated the return structure (e.g., array of objects) to fully compensate for the missing output schema.

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 input schema contains zero parameters, so there is no additional parameter semantics to convey beyond the baseline. The description appropriately does not invent parameters where none exist.

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 uses the specific verb 'List' with the clear resource scope 'loaded MCP server plugins and their versions.' It effectively distinguishes itself from siblings like list_apps, list_devices, and list_files by explicitly mentioning 'MCP server plugins' rather than device-side entities.

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 explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or conditions where it might be preferred over other listing tools like list_apps.

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/divineDev-dotcom/android_mcp'

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