Skip to main content
Glama
kajirita2002

honeycomb-mcp-server

honeycomb_trigger_create

Generate alerts for dataset changes by creating triggers with customizable thresholds, schedules, and notification settings using a specified query or query ID.

Instructions

Create a new trigger for a dataset

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
alert_typeNoAlert firing behavior: on_change (only when crossing threshold) or on_true (every check while threshold is met)on_change
datasetSlugYesDataset slug to create trigger for
descriptionNoDescription of the trigger (max 1023 chars)
disabledNoIf true, the trigger will not be evaluated or send alerts
evaluation_scheduleNoSchedule configuration when evaluation_schedule_type is 'window'
evaluation_schedule_typeNoThe schedule type: frequency (always run) or window (only run during specific times)
frequencyNoInterval in seconds to check results (60-86400, must be multiple of 60)
nameYesName of the trigger (max 120 chars)
queryNoInline query specification (use either query or query_id, not both)
query_idNoQuery ID to associate with the trigger (use either query_id or query, not both)
recipient_idsNoRecipient IDs to notify when the trigger fires
thresholdNoThreshold configuration for the trigger
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states this creates something (implying a write operation) but doesn't disclose authentication requirements, rate limits, error conditions, what happens on success (e.g., returns trigger ID), or whether this operation is idempotent. For a creation tool with complex parameters, this is inadequate.

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 with zero wasted words. It's perfectly front-loaded with the core action and resource, making it immediately understandable despite its brevity.

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?

For a complex creation tool with 12 parameters (including nested objects), no annotations, and no output schema, the description is severely incomplete. It doesn't explain what a trigger is, what it does, typical use cases, or what information the agent should expect in return. The agent would struggle to use this tool effectively without additional context.

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 the schema fully documents all 12 parameters. The description adds no parameter-specific information beyond what's in the schema, but doesn't need to since schema coverage is complete. The baseline of 3 is appropriate when the schema does all the work.

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 action ('Create') and resource ('new trigger for a dataset'), making the purpose understandable. However, it doesn't differentiate this tool from its sibling 'honeycomb_trigger_update' or explain what a 'trigger' specifically is in the Honeycomb context, which would be needed for a perfect 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 like 'honeycomb_trigger_update' or 'honeycomb_slo_create'. It doesn't mention prerequisites (e.g., needing an existing dataset) or typical use cases for creating triggers versus other alerting mechanisms.

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

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