Skip to main content
Glama

list_agent_triggers

Read-only

Lists Otto/Now Assist AI agent triggers—record-based, scheduled, and channel—to show which agentic workflows they start and allow filtering by target table, active status, or use case.

Instructions

List Otto / Now Assist AI agent triggers (sn_aia_trigger_configuration): record-based, scheduled and channel triggers that start agentic workflows, with their target table, condition, run-as user and linked use cases/agents (sn_aia_trigger_agent_usecase_m2m).

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": "list_agent_triggers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax records (default 50)
queryNoExtra encoded query
activeNoFilter on active
usecaseNoFilter by agentic workflow / use case sys_id (sn_aia_usecase)
target_tableNoFilter by the table the trigger watches, e.g. incident

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scope about what is returned — target table, condition, run-as user, and the linked use cases/agents joined via sn_aia_trigger_agent_usecase_m2m — but says nothing about pagination behavior or result volume beyond the schema's limit default.

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?

A single front-loaded sentence that leads with the verb and resource, then layers detail. It is dense but every clause carries information; only the parenthetical table names could be seen as clutter.

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

Completeness4/5

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

For a parameterless-required, read-only list tool with full schema coverage and no output schema, the description supplies enough: what is listed, which table, the trigger categories, and the relationship join. Minor gaps are pagination/result-size expectations, which the schema's limit default partly covers.

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 all five parameters are self-documenting and baseline is 3. The description reinforces the 'target table' and 'use case' filters conceptually, but adds no syntax, encoding, or edge-case detail (e.g. how query composes with the other filters) beyond the schema.

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 names a specific verb and resource ('List Otto / Now Assist AI agent triggers') and even pins the underlying table (sn_aia_trigger_configuration), then enumerates the trigger kinds (record-based, scheduled, channel) and the payload fields returned. An agent can distinguish this from sibling listers like list_agent_use_cases or list_ai_agents purely from the text.

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?

Usage is implied by the resource name — an agent that needs to see triggers rather than use cases or agents would pick this. However, there is no explicit when-to-use, no exclusions, and no pointer to a sibling for a related question (e.g. fetching an individual trigger or its agent links).

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