Skip to main content
Glama
Heliyos MCP server

Heliyos MCP server

Official
by heliyos-ai

List worker triggers

heliyos_triggers_list
Read-onlyIdempotent

Lists available event, mention, and schedule triggers with meanings and object types so you can pick the right events before creating or updating a worker.

Instructions

Lists the events a worker can subscribe to (the names to put in an event trigger's events on heliyos_workers_create / heliyos_workers_update), each with what it means and the object it is about. Also lists the mention and schedule kinds. Call it before creating a worker that reacts to events. Returns every trigger in one page. Returns structuredContent {triggers:[{name, kind, label, description, object_type, ...}]}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "heliyos_triggers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly event, mention or schedule triggers.
object_typeNoOnly triggers about this object: company, people, deals, task, note, interaction, review, signal, ...

Output Schema

NameRequiredDescriptionDefault
triggersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: results come back in a single page with no pagination, and the payload is structuredContent with a named triggers array. It does not discuss auth or rate limits, but those are not material for a static catalog read.

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 purpose and the call-before-creating guidance are front-loaded, and the return-shape note comes last where it belongs. The two closing sentences about paging and structuredContent overlap slightly, which is the only waste.

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?

For a two-parameter, read-only catalog tool with an output schema, the description covers purpose, when to call, filtering scope, and return shape. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns an extra point by explaining what the filters mean in context: kind covers event/mention/schedule and object_type scopes to the object the trigger is about. It does not add syntax or format detail beyond the schema, so it stops short of 5.

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 states a specific verb and resource ('Lists the events a worker can subscribe to') and immediately ties it to the sibling tools that consume the output (heliyos_workers_create / heliyos_workers_update). It also clarifies the scope includes mention and schedule kinds, so an agent can distinguish it from unrelated list tools.

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?

It gives an explicit call condition: 'Call it before creating a worker that reacts to events.' That is clear when-to-use guidance tied to a concrete workflow. It does not state when not to call it or name an alternative source for the same data, which keeps it short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools