Skip to main content
Glama
honeycombio
by honeycombio

list_recipients

Retrieve available notification recipients for a specific Honeycomb environment, including names, types, targets, and metadata, with pagination and search capabilities.

Instructions

Lists available recipients for notifications in a specific environment. This tool returns a list of all recipients available in the specified environment, including their names, types, targets, and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environmentYesThe Honeycomb environment
pageNoPage number (1-based)
limitNoNumber of items per page
sort_byNoField to sort by
sort_orderNoSort direction
searchNoSearch term to filter results
search_fieldsNoFields to search in (string or array of strings)

Implementation Reference

  • The handler function that executes the list_recipients tool logic: validates input, fetches recipients via API, simplifies data, and returns formatted response.
    handler: async ({ environment }: z.infer<typeof ListRecipientsSchema>) => {
      // Validate input parameters
      if (!environment) {
        return handleToolError(new Error("environment parameter is required"), "list_recipients");
      }
    
      try {
        // Fetch recipients from the API
        const recipients = await api.getRecipients(environment);
        
        // Create a simplified response
        const simplifiedRecipients = recipients.map(recipient => ({
          id: recipient.id,
          name: recipient.name,
          type: recipient.type,
          target: recipient.target || '',
          created_at: recipient.created_at,
          updated_at: recipient.updated_at,
        }));
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(simplifiedRecipients, null, 2),
            },
          ],
          metadata: {
            count: simplifiedRecipients.length,
            environment
          }
        };
      } catch (error) {
        return handleToolError(error, "list_recipients");
      }
    }
  • Zod schema for list_recipients tool inputs: requires 'environment', merges optional pagination parameters.
    export const ListRecipientsSchema = z.object({
      environment: z.string().min(1).trim().describe("The Honeycomb environment"),
    }).merge(PaginationSchema).describe("Parameters for listing notification recipients in a Honeycomb environment. Recipients receive alerts from triggers.");
  • Registration of the list_recipients tool: created via createListRecipientsTool(api) and added to the tools array in registerTools function, which registers all tools with the MCP server via a loop.
    // Recipient tools
    createListRecipientsTool(api),
Behavior2/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 mentions the return format ('list of all recipients... including their names, types, targets, and metadata') but lacks critical behavioral details: pagination behavior (implied by 'page' and 'limit' parameters but not explained), rate limits, authentication requirements, or error conditions. This is inadequate for a tool with 7 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences that efficiently state the purpose and return format. It's front-loaded with the core functionality. No wasted words, though it could be slightly more structured (e.g., separating purpose from output details).

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

Completeness2/5

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

Given 7 parameters, no annotations, and no output schema, the description is incomplete. It covers the basic purpose and return fields but misses behavioral context (pagination, errors, auth), parameter interactions, and comparison to siblings. For a list tool with filtering/sorting parameters, more guidance is needed.

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?

Schema description coverage is 100%, so parameters are fully documented in the schema. The description adds no parameter-specific semantics beyond implying filtering via 'search' and pagination via 'page'/'limit'. It meets the baseline for high schema coverage but doesn't enhance understanding of parameter interactions or constraints.

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: 'Lists available recipients for notifications in a specific environment.' It specifies the verb ('Lists'), resource ('recipients'), and scope ('in a specific environment'). However, it doesn't explicitly differentiate from sibling tools like 'list_boards' or 'list_triggers' beyond the 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 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 (e.g., environment access), exclusions, or related tools for notification management. The agent must infer usage from the purpose alone.

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/honeycombio/honeycomb-mcp'

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