action1-mcp-server

Get diagnostic logs

action1_list_logs

Read-onlyIdempotent

Retrieve detailed diagnostic logs to diagnose system behavior. Filter results by severity, organization, or record range to identify and resolve operational errors.

Instructions

Get diagnostic logs. Gets diagnostic logs. Use parameters to pre-filter returned results. Perm: manage_endpoints.

Input Schema

Name	Required	Description
`from`	No	Provide the number of the first record to be returned.
`level`	No	Specify the minimum request level.
`limit`	No	Set the maximum number of items to be returned (the page size).
`cursor`	No	next_cursor of the previous call; takes precedence over from.
`org_id`	No	Org UUID.
`sortby`	No	Define the sorting order by a certain field.
`verbose`	No	Skip per-item compactor.
`auto_paginate`	No	Walk pages until limit or the size budget; then continue with next_cursor.
`response_format`	No	Output format. Default markdown.

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.

Changed12 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 / auto_paginate / description

Previous value: -"Walk all pages."New value: +"Walk pages until limit or the size budget; then continue with next_cursor."

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor."New value: +"next_cursor of the previous call; takes precedence over from."

addedInput schema / properties / from / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / from / minimum
```
Added value: +0
```

addedInput schema / properties / level / enum

Added value: +[
+  "Debug",
+  "Normal",
+  "Internal",
+  "Important",
+  "Error",
+  "Critical"
+]

addedInput schema / properties / limit / maximum
```
Added value: +50000
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

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 / properties

Added value: +{
+  "endpoint_id": {},
+  "endpoint_name": {},
+  "id": {},
+  "is_connector": {},
+  "level": {},
+  "message": {},
+  "self": {},
+  "time": {},
+  "type": {}
+}

First observedv0.5.0Jun 27, 2026

TDQS

C2.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 one genuine addition is "Perm: manage_endpoints", which tells the agent an authorization scope annotations cannot express. Nothing is said about pagination behavior (from/cursor/auto_paginate interplay) or what the logs contain, so credit is limited.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are a duplicated restatement of the title, which is pure waste, and the remaining content is thin. It is short, but shortness here comes from under-specification rather than tight writing.

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?

An output schema exists and all parameters are documented, so the description needn't explain returns. It still omits default scoping (which org, whether all orgs are covered) and pagination guidance, which matter for a nine-parameter log-listing tool with an open-world hint.

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% and all nine parameters are individually documented, so the schema does the heavy lifting. The description adds no meaning beyond the schema — it does not explain the from-vs-cursor precedence, the level semantics, or paging limits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (diagnostic logs) with an implicit read verb, so an agent can tell it retrieves rather than mutates logs. But the first two sentences say the same thing verbatim, adding no scope, source, or differentiation from log-adjacent siblings like action1_list_audit_events or action1_audit_log_search.

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?

"Use parameters to pre-filter returned results" is the only usage guidance, and it restates the obvious fact that optional query params filter results. There is no statement of when to pick this over the audit-log tools, no prerequisites, and no exclusions.

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

Deploy Server