Skip to main content
Glama
WYRE-AI

Slide MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

slide_list_audit_logs

Retrieve audit log entries with filters for action, resource type, client, and time range to track changes in Slide backup/BDR environments.

Instructions

List audit log entries, filterable by action name, resource type, client, and audit-time range.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of items to return per page. Defaults to 10.
offsetNoStarting index for pagination. Defaults to 0.
sort_byNoField to sort by. Defaults to "audit_time".
sort_ascNoSort in ascending order. Defaults to false (descending).
client_idNoFilter by client.
audit_time_afterNoFilter audit logs to after a specific audit timestamp (RFC3339 format).
audit_action_nameNoFilter by audit action name (see slide_list_audit_actions).
audit_time_beforeNoFilter audit logs to before a specific audit timestamp (RFC3339 format).
audit_resource_type_nameNoFilter by audit resource type name (see slide_list_audit_resource_types).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. 'List' and 'filterable' indicate a read-only query operation with no destructive side effects, which is transparent enough for a simple list tool. Still, it does not mention pagination behavior, default ordering, response shape, or any rate-limit/auth considerations beyond what the schema already states.

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?

The description is a single, front-loaded sentence: it leads with the action and resource, then lists the main filtering capabilities. There is no filler, repetition, or vague language; every word earns its place.

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 read-only list tool with no required parameters and a fully described schema, this one-sentence description covers the core selection and invocation needs. It does not mention the singular get tool or helper list tools, but the resource name, list semantics, and parameter descriptions make the tool usable without those references.

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 parameters are already well documented. The description summarizes the filter axes ('action name, resource type, client, and audit-time range') but adds no new meaning beyond the schema. This matches the baseline for high schema coverage.

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 uses a specific verb and resource: 'List audit log entries,' which clearly identifies the operation. It adds the key filter dimensions (action name, resource type, client, audit-time range), making it distinguishable from the singular slide_get_audit_log sibling. It does not explicitly mention that sibling or describe return fields, so it misses full distinction.

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?

The description implies usage for retrieving multiple audit log entries and suggests filtering, which provides basic context. However, it does not explicitly state when to prefer this tool over slide_get_audit_log, nor does it mention related helper tools like slide_list_audit_actions. The usage is inferred rather than explicitly guided.

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