action1-mcp-server

Search the audit log

action1_audit_log_search

Read-onlyIdempotent

Search Action1 audit events by time window and case-insensitive user, event, or object filters to find relevant activity.

Instructions

Search /audit/events with an optional time window (sent to Action1 as timefrom/timeto) and case-insensitive substring filters on user, event and object.

Input Schema

Name	Required	Description
`limit`	No	Max items.
`cursor`	No	Pagination cursor.
`to_time`	No	Upper bound: YYYY-MM-DD_HH-MM-SS (UTC) or ISO-8601.
`from_time`	No	Lower bound: YYYY-MM-DD_HH-MM-SS (UTC) or ISO-8601.
`user_substring`	No	Filter by user name.
`response_format`	No	Output format. Default markdown.
`target_substring`	No	Filter by affected object (name, URL or description).
`event_type_substring`	No	Filter by event name (e.g. Login, View Report, POST).

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`items`	Yes
`total`	No
`has_more`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.6.0Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / event_type_substring / description

Previous value: -"Filter by event_type."New value: +"Filter by event name (e.g. Login, View Report, POST)."

changedInput schema / properties / from_time / description

Previous value: -"ISO-8601 lower bound."New value: +"Lower bound: YYYY-MM-DD_HH-MM-SS (UTC) or ISO-8601."

removedInput schema / properties / from_time / format
```
Removed value: -"date-time"
```

addedInput schema / properties / from_time / pattern

Added value: +"^(?:\\d{4}-\\d{2}-\\d{2}_\\d{2}-\\d{2}-\\d{2}|\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d+)?(?:Z|[+-]\\d{2}:?\\d{2}))$"

changedInput schema / properties / target_substring / description

Previous value: -"Filter by target."New value: +"Filter by affected object (name, URL or description)."

changedInput schema / properties / to_time / description

Previous value: -"ISO-8601 upper bound."New value: +"Upper bound: YYYY-MM-DD_HH-MM-SS (UTC) or ISO-8601."

removedInput schema / properties / to_time / format
```
Removed value: -"date-time"
```

addedInput schema / properties / to_time / pattern

Added value: +"^(?:\\d{4}-\\d{2}-\\d{2}_\\d{2}-\\d{2}-\\d{2}|\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d+)?(?:Z|[+-]\\d{2}:?\\d{2}))$"

changedInput schema / properties / user_substring / description

Previous value: -"Filter by user."New value: +"Filter by user name."

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
addedOutput schema / properties / items / items / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

First observedv0.5.0Jun 27, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds useful semantics: filters are case-insensitive and the time bounds are translated to Action1's timefrom/timeto. It says nothing about result ordering, cursor behavior, or result volume on a readOnly search, which would have raised this.

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?

A single front-loaded sentence naming the endpoint, the optional time window, and the three filter families. No filler, and the most important scoping detail comes first.

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?

With rich annotations, a full output schema, and 100% schema description coverage, the description only needs to add filter semantics, which it does. The remaining gap is sibling disambiguation against the other audit-log tools, so it is not quite complete.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by specifying that substring filters are case-insensitive and that from_time/to_time are sent as timefrom/timeto. That clarifies matching behavior the schema only names generically ('Filter by user name').

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?

States a specific verb+resource ('Search /audit/events') and enumerates the filter dimensions (time window, user, event, object). It does not differentiate itself from the closely named siblings list_audit_events, export_audit_log or get_audit_event, so an agent still has to infer the boundary.

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 presence of an 'optional' time window and substring filters implies the use case (narrowing a large audit log), but there is no explicit statement of when to prefer this over action1_list_audit_events, action1_export_audit_log, or action1_get_audit_event for single records. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server