remnus

query_audit_log

Read-only

Agent activity log for this workspace, filterable by tool, status and date range.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "query_audit_log"
  }
}

Input Schema

Name	Required	Description
`to`	No	ISO 8601
`from`	No	ISO 8601
`tool`	No	Tool name
`limit`	No
`status`	No

Output Schema

Name	Required	Description	Default
`entries`	Yes	Newest first

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 24, 2026

changedInput schema / properties / from / description

Previous value: -"Start of date range (ISO 8601, e.g. \"2025-01-01T00:00:00Z\")"New value: +"ISO 8601"

removedInput schema / properties / limit / description
```
Removed value: -"Maximum results (default 50)"
```
removedInput schema / properties / status / description
```
Removed value: -"Filter by call status"
```

changedInput schema / properties / to / description

Previous value: -"End of date range (ISO 8601, e.g. \"2025-12-31T23:59:59Z\")"New value: +"ISO 8601"

changedInput schema / properties / tool / description

Previous value: -"Filter by tool name (e.g. \"create_page\", \"query_database\")"New value: +"Tool name"

Changed9 schema fields changedJul 8, 2026
- changedOutput schema / properties / entries / description
```
Previous value: -"Audit log entries, newest first"New value: +"Newest first"
```
- removedOutput schema / properties / entries / items / properties / agentName / description
```
Removed value: -"Agent brand id"
```
- removedOutput schema / properties / entries / items / properties / createdAt / description
```
Removed value: -"When the call happened"
```
- removedOutput schema / properties / entries / items / properties / id / description
```
Removed value: -"Activity row ID"
```
- changedOutput schema / properties / entries / items / properties / status / description
```
Previous value: -"Call status (success | error)"New value: +"success | error"
```
- removedOutput schema / properties / entries / items / properties / targetId / description
```
Removed value: -"Target resource ID"
```
- removedOutput schema / properties / entries / items / properties / targetType / description
```
Removed value: -"Target resource type"
```
- removedOutput schema / properties / entries / items / properties / tokenName / description
```
Removed value: -"Token label"
```
- removedOutput schema / properties / entries / items / properties / tool / description
```
Removed value: -"Tool that was called"
```
First observedJun 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds context by noting the log is workspace-scoped and filterable by tool, status, and date range, which is useful but not deeply behavioral. No contradiction with annotations.

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 that communicates the resource scope and key filtering capabilities without excess. Every part adds useful information.

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?

The description is sufficient for selecting and invoking this low-complexity tool: it names the workspace scope and filter dimensions, and the output schema and input schema cover the remaining details. Limit is not mentioned, but its default and role are apparent from the schema.

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 60%, so the schema carries much of the parameter explanation. The description adds a helpful mapping by naming 'tool, status and date range,' aligning with tool, status, to, and from, but it does not clarify limit or provide deeper parameter semantics.

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 identifies the resource as the 'Agent activity log for this workspace' and conveys that it is queryable via filtering. It does not explicitly contrast with sibling tools, but the subject matter is distinct enough from query_database and search_workspace to be understood.

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: use it when you need an agent activity log for the workspace. It mentions filter dimensions but provides no explicit guidance on when to prefer an alternative tool or when not to use this tool.

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

All remnus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.