Skip to main content
Glama
TsvetanG2

cognigy-ai-mcp-management-server

list_audit_events

Read-onlyIdempotent

Retrieve a record of user modifications to Cognigy.AI resources (flows, intents, endpoints) for compliance and debugging.

Instructions

Lists Cognigy.AI audit events. Audit events track all changes made to resources (flows, intents, endpoints, etc.) by users. Useful for compliance and debugging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of items to skip for pagination
limitNoMaximum number of events to return (default: 25, max: 100)
userIdNoFilter audit events by user ID
endDateNoEnd date for audit events (ISO 8601 format)
eventTypeNoFilter by event type (e.g., 'create', 'update', 'delete')
projectIdNoFilter audit events by project ID
startDateNoStart date for audit events (ISO 8601 format)
resourceTypeNoFilter by resource type (e.g., 'flow', 'intent', 'endpoint')
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds context about tracking changes but does not detail behavior like pagination or data scope beyond what annotations provide.

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?

Three sentences, no redundant information, directly states purpose and value.

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

Completeness3/5

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

No output schema; description omits response structure. Context on filtering and pagination is implied by parameter descriptions but not expanded on.

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?

All 8 parameters have full descriptions in input schema (100% coverage). Description adds no additional parameter info 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?

Clear verb 'Lists' and resource 'audit events' specified. Distinguishes from sibling tools that list specific resources like list_flows or list_intents.

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?

Implied use for compliance and debugging, but no explicit when/why or comparison to alternatives among many sibling tools.

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/TsvetanG2/cognigy-ai-mcp-management-server'

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