Skip to main content
Glama

list_services

Retrieve a list of configured webhook services and auto-detected defaults for sending notifications to Discord or Slack with secure management and validation.

Instructions

List configured webhook services and auto-detected default

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_services' tool. It calls getServiceStatus() to retrieve the configuration status of Discord and Slack services and returns the result as a formatted JSON text block.
    async () => {
      const status = getServiceStatus();
      
      const result = {
        discordConfigured: status.discordConfigured,
        slackConfigured: status.slackConfigured, 
        autoDefault: status.autoDefault,
        bothConfigured: status.bothConfigured
      };
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2)
          }
        ]
      };
    }
  • src/index.ts:25-49 (registration)
    Registration of the 'list_services' tool using server.tool(), including description, empty input schema, and inline handler function.
    // Tool: list_services  
    server.tool(
      "list_services",
      "List configured webhook services and auto-detected default",
      {},
      async () => {
        const status = getServiceStatus();
        
        const result = {
          discordConfigured: status.discordConfigured,
          slackConfigured: status.slackConfigured, 
          autoDefault: status.autoDefault,
          bothConfigured: status.bothConfigured
        };
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      }
    );
  • Zod schema definition for the 'list_services' tool input parameters (empty object as no inputs are required).
    export const ListServicesSchema = z.object({});
  • Helper function getServiceStatus() that provides the service configuration status used by the list_services handler.
    export function getServiceStatus(): {
      discordConfigured: boolean;
      slackConfigured: boolean;
      autoDefault: Service;
      bothConfigured: boolean;
    } {
      const config = getConfig();
      
      return {
        discordConfigured: !!config.discordWebhookUrl,
        slackConfigured: !!config.slackWebhookUrl,
        autoDefault: config.autoDefault,
        bothConfigured: !!(config.discordWebhookUrl && config.slackWebhookUrl),
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions listing both configured and auto-detected services, which adds some behavioral context, but doesn't disclose critical details like whether this is a read-only operation, potential rate limits, authentication needs, or what the output format looks like. For a tool with zero annotation coverage, this is insufficient.

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 directly states the tool's function without any wasted words. It's front-loaded and appropriately sized for its simple purpose.

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 simplicity (0 parameters, no annotations, no output schema), the description is adequate but has gaps. It explains what is listed but doesn't cover behavioral aspects like safety or output format. For a list operation, more context on what 'configured' and 'auto-detected' entail would improve completeness.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but since there are no parameters, the baseline is high. It could be a 5 if it explicitly stated 'no parameters required', but it's still very clear in context.

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 'List' and the resource 'configured webhook services and auto-detected default', making the purpose understandable. However, it doesn't explicitly distinguish this tool from its siblings (send_notification, validate_webhook), which are clearly different operations, 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. It doesn't mention prerequisites, context for listing services, or compare it to sibling tools like send_notification or validate_webhook, leaving usage decisions to inference.

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

Related 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/thesammykins/notifyme_mcp'

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