Skip to main content
Glama
navin2031992

iSuite Operations MCP Server

by navin2031992

search_audit_logs

Search and filter iSuite audit trail logs by user, action, resource, date range, and outcome to investigate events.

Instructions

Search iSuite audit trail logs with flexible filtering across users, actions, and time ranges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text search query against log message and metadata fields.
userIdNoFilter logs by the user who performed the action.
actionNoFilter by action type (e.g. 'LOGIN', 'USER_CREATE', 'JOB_CANCEL', 'CONFIG_UPDATE').
resourceTypeNoFilter by resource type (e.g. 'user', 'job', 'batch', 'schedule', 'config').
resourceIdNoFilter by specific resource ID.
dateFromNoISO-8601 start datetime for the search window.
dateToNoISO-8601 end datetime (default: now).
outcomeNoFilter by outcome of the action (default 'all').
limitNoMaximum results to return (default 100, max 1000).
offsetNoPagination offset (default 0).
Behavior2/5

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

No annotations present; description does not disclose behavior such as read-only nature, pagination defaults, or permission requirements. 'Flexible filtering' is vague.

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?

One concise sentence front-loading the purpose. Efficient but slightly vague on 'flexible filtering' details.

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

Completeness2/5

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

With 10 parameters and no output schema or annotations, the description is too brief. Missing details on return format, pagination behavior, and usage examples.

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 coverage is 100% with clear parameter descriptions. The tool description adds only generic context ('flexible filtering'), not meaningfully beyond 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 clearly states the tool searches audit trail logs with flexible filtering, distinguishing it from sibling tools like get_audit_log (single log) and export_audit_trail (export).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., export_audit_trail, get_audit_log). No exclusion criteria or context provided.

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/navin2031992/mcpisuite'

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