Skip to main content
Glama

getEnabledTools

Read-onlyIdempotent

Identify available alternatives when a requested tool is unavailable. Returns information about which tools are enabled in the full and minimal tool sets.

Instructions

IMPORTANT: Run this tool first when a requested tool is unavailable. Returns information about which tools are enabled in the full and minimal tool sets, helping you identify available alternatives.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that returns information about enabled tools across full, minimal, and excluded sets, along with server context info.
    export async function handler(
      _args: z.infer<typeof parameters>,
      extra: { client: PostmanAPIClient; headers?: IsomorphicHeaders; serverContext?: ServerContext }
    ): Promise<CallToolResult> {
      try {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(
                {
                  serverInfo: extra.serverContext
                    ? {
                        serverType: extra.serverContext.serverType,
                        currentServerTools: extra.serverContext.availableTools,
                        currentServerToolCount: extra.serverContext.availableTools.length,
                      }
                    : {
                        serverType: 'unknown',
                        note: 'Server context not available',
                      },
                  enabledTools: {
                    full: Array.from(enabledResources.full),
                    minimal: Array.from(enabledResources.minimal),
                    excludedFromGeneration: Array.from(enabledResources.excludedFromGeneration),
                  },
                  stats: {
                    totalFull: enabledResources.full.length,
                    totalMinimal: enabledResources.minimal.length,
                    totalExcludedFromGeneration: enabledResources.excludedFromGeneration.length,
                  },
                },
                null,
                2
              ),
            },
          ],
        };
      } catch (e: unknown) {
        if (e instanceof McpError) {
          throw e;
        }
        throw asMcpError(e);
      }
    }
  • Input schema: no parameters required (empty Zod object).
    export const parameters = z.object({});
  • Tool registration constants: method name and description exported as module-level exports.
    export const method = 'getEnabledTools';
  • Enabled resources configuration that includes 'getEnabledTools' in the full, minimal, and excludedFromGeneration sets.
    export const enabledResources = {
      full,
      minimal,
      code,
      excludedFromGeneration,
      subtools,
      templated,
    };
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, indicating safe read behavior. The description adds value by specifying it returns information about enabled tool sets, which is behavioral context beyond what annotations provide.

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 important usage highlighted upfront. Every sentence provides necessary information without redundancy.

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

Completeness5/5

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

The description fully covers the tool's purpose, usage guidance, and output, given its zero parameters and simple intent. No additional 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?

No parameters exist, and schema coverage is 100%, so no additional parameter information is needed. Baseline score of 4 is appropriate given the tool requires no input.

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 tool's purpose: returns information about enabled tools, and specifies when to use it (when a requested tool is unavailable). It effectively distinguishes itself from sibling tools by addressing tool availability rather than data objects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states to run this tool first when a requested tool is unavailable, providing clear context and helping identify alternatives. While it doesn't explicitly exclude other scenarios, the guidance is sufficiently practical.

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/postmanlabs/postman-mcp-server'

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