Skip to main content
Glama

get_event_handlers

Retrieve or filter event handlers that define how Conductor responds to external events, with options to specify event names and active status.

Instructions

Get all event handlers or filter by event and active status. Event handlers define how Conductor responds to external events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventNoFilter by event name
activeOnlyNoReturn only active event handlers (default: true)

Implementation Reference

  • Handler implementation for get_event_handlers: extracts event and activeOnly parameters, calls Conductor API endpoint /event, and returns the JSON response as text content.
    case "get_event_handlers": {
      const params: any = {};
      
      if ((args as any).event) params.event = (args as any).event;
      if ((args as any).activeOnly !== undefined) params.activeOnly = (args as any).activeOnly;
      else params.activeOnly = true;
      
      const response = await conductorClient.get("/event", { params });
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:562-580 (registration)
    Tool registration in the tools array, including name, description, and input schema for get_event_handlers.
      {
        name: "get_event_handlers",
        description:
          "Get all event handlers or filter by event and active status. Event handlers define how Conductor responds to external events.",
        inputSchema: {
          type: "object",
          properties: {
            event: {
              type: "string",
              description: "Filter by event name",
            },
            activeOnly: {
              type: "boolean",
              description: "Return only active event handlers (default: true)",
            },
          },
        },
      },
    ];
  • Input schema definition for the get_event_handlers tool.
        inputSchema: {
          type: "object",
          properties: {
            event: {
              type: "string",
              description: "Filter by event name",
            },
            activeOnly: {
              type: "boolean",
              description: "Return only active event handlers (default: true)",
            },
          },
        },
      },
    ];
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 of behavioral disclosure. It mentions the tool can 'get all event handlers or filter,' but doesn't specify whether this is a read-only operation, if it requires authentication, what the return format is (e.g., list, pagination), or any rate limits. For a tool with no annotations, this is a significant gap in transparency.

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 concise and well-structured in two sentences: the first states the purpose and filtering options, and the second explains what event handlers are. Every sentence adds value without redundancy, making it efficient and front-loaded.

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 moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and filtering, but lacks details on behavioral aspects like return format, permissions, or error handling. Without annotations or output schema, more context would be beneficial for completeness.

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 description mentions filtering by 'event and active status,' which aligns with the two parameters in the schema (event, activeOnly). Since schema description coverage is 100%, the schema already documents these parameters fully. The description adds no additional semantic context beyond what the schema provides, so the baseline score of 3 is appropriate.

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 tool's purpose: 'Get all event handlers or filter by event and active status.' It specifies the verb ('Get') and resource ('event handlers'), and explains what event handlers are ('define how Conductor responds to external events'). However, it doesn't explicitly differentiate from sibling tools (e.g., get_task_definition, get_workflow_definition), which prevents a score of 5.

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 context by mentioning filtering options ('filter by event and active status'), but doesn't provide explicit guidance on when to use this tool versus alternatives like get_task_definition or get_workflow_definition. It also doesn't mention prerequisites or exclusions, leaving usage somewhat ambiguous.

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/opensensor/conductor-mcp'

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