Skip to main content
Glama
CSOAI-ORG

Slack Enterprise MCP Server

get_audit_log

Retrieve the audit trail of all MCP actions performed through this server for compliance monitoring. Filter by action name to see who did what and when.

Instructions

Return the audit trail of all MCP actions performed through this server. Enterprise compliance feature -- shows who did what and when. Optionally filter by action name (e.g. 'send_message', 'create_channel').

Behavior: This tool generates structured output without modifying external systems. Output is deterministic for identical inputs. No side effects. Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results.

Args: limit (int): The limit to analyze or process. action_filter (str): The action filter to analyze or process. api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
action_filterNo
api_keyNo
Behavior5/5

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

With no annotations, the description carries full burden and excels: it explicitly states read-only nature, no side effects, rate limits (10/day free, unlimited pro), authentication details, error handling, and idempotency. This is comprehensive and exceeds requirements.

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?

The description is lengthy with redundancy between 'Behavior' and 'Behavioral Transparency' sections. The 'Args' section is unnecessary given schema. It is structured with headings, but could be more concise without losing key information.

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?

Covers many aspects (purpose, behavior, rate limits, error handling, privacy) but lacks details on parameters and output structure. No output schema exists, and the description does not describe what fields are returned. Parameter descriptions are insufficient. Overall, adequate but with gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the 'Args' section only repeats parameter names with generic phrases like 'The limit to analyze or process,' adding no meaningful semantics. The description does not explain what 'limit' means in context (e.g., number of records), nor what valid action_filter values are. Minimal value added over schema.

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 'Return the audit trail of all MCP actions performed through this server,' which is a specific verb+resource. It distinguishes from sibling tools like send_message or list_channels by focusing on compliance auditing. However, the 'When to use' section is generic and misaligned, slightly reducing clarity.

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?

Includes explicit 'When to use' and 'When NOT to use' sections, but the 'When to use' is vague and not specific to audit logs, saying 'structured analysis or classification of inputs'—which doesn't match the tool's purpose. No comparison with sibling tools is provided, limiting differentiation.

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/CSOAI-ORG/slack-enterprise-mcp'

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