Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

list_workflow_events

Retrieve workflow automation triggers to initiate compliance processes. Access system events for assessment completions and form submissions, plus custom events for external integrations and manual execution.

Instructions

Retrieve available workflow events that can trigger workflows.

Events are the starting points of workflows. Each event has a payload that provides data to subsequent workflow nodes. Events are categorized into two types:

System Events: Automatically triggered by the system when specific actions occur. Examples include:

  • Assessment run completed

  • Form submitted

  • Scheduled time-based triggers

Custom Events: Manually triggered events that can be used to:

  • Trigger workflows from within other workflows

  • Integrate with external systems

  • Enable manual workflow execution

Returns: - systemEvents (List[WorkflowEventVO]): A list of system events that are automatically triggered. - id (str) - categoryId (str) - desc (str) - displayable (str) - payload [List[WorkflowPayloadVO]] - status (str) - type (str) - customEvents (List[WorkflowEventVO]): A list of custom events that can be manually triggered. - id (str) - categoryId (str) - desc (str) - displayable (str) - payload [List[WorkflowPayloadVO]] - status (str) - type (str) - error (Optional[str]): An error message if any issues occurred during retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
systemEventsNo
customEventsNo
errorNo
Behavior4/5

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

With no annotations provided, description carries full burden by detailing the read-only nature and return structure (system vs custom events), though could explicitly state idempotency or caching behavior.

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

Conciseness3/5

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

Well-structured with clear categorization, but overly verbose due to extensive Returns section that duplicates what should be in the output schema (per 100% schema coverage signal).

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?

Complete for the tool's complexity, covering domain concepts (System vs Custom events) and payload structure, though return value detail is excessive given output schema exists.

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?

Baseline score for zero-parameter tool; no parameters require explanation.

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?

Clearly states the tool retrieves available workflow events with specific verb+resource, and distinguishes from siblings like create_workflow_custom_event or trigger_workflow by focusing on retrieval of event definitions.

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?

Explains what events are (starting points) and categorizes them, but lacks explicit guidance on when to use this vs alternatives like list_workflow_event_categories or before creating workflows.

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/ComplianceCow/cow-mcp'

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