tslink

Overview Schema Source Related Servers Discussions Admin

Summarize access logs

access_summary

Read-onlyIdempotent

Aggregate local access events into audit counts and traffic by login and app, so you can review totals, trends and last allowed access without inspecting individual entries.

Instructions

Aggregate matching local access events into audit counts and traffic: HTTP requests, upload/download bytes and last request/allowed times by canonical login and app, with separate public/tagged/unknown buckets and TCP counters. Use access_summary for totals and trends; use access_log for individual events. Summaries cover all matches regardless of the event limit; denied events do not advance last allowed access. No credentials, network calls or writes; suitable for viewer scopes. Query strings, headers and bodies are absent.

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": "access_summary"
  }
}

Input Schema

Name	Required	Description	Default
`app`	No
`who`	No
`limit`	No
`since`	No
`until`	No
`decision`	No

Output Schema

Name	Required	Description	Default
`apps`	Yes
`count`	Yes
`denied`	Yes
`people`	Yes
`allowed`	Yes
`reasons`	No
`traffic`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.0Oct 27, 2026

addedOutput schema / properties / reasons
```
Added value: +{
+  "type": "array"
+}
```

addedOutput schema / properties / traffic

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "apps": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "allowed": {
+            "type": "integer"
+          },
+          "app": {
+            "type": "string"
+          },
+          "bytes_in": {
+            "type": "integer"
+          },
+          "bytes_out": {
+            "type": "integer"
+          },
+          "denied": {
+            "type": "integer"
+          },
+          "last_allowed_at": {
+            "format": "date-time",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_request_at": {
+            "format": "date-time",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "requests": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "app",
+          "requests",
+          "allowed",
+          "denied",
+          "bytes_in",
+          "bytes_out",
+          "last_request_at",
+          "last_allowed_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "http": {
+      "additionalProperties": false,
+      "properties": {
+        "allowed": {
+          "type": "integer"
+        },
+        "bytes_in": {
+          "type": "integer"
+        },
+        "bytes_out": {
+          "type": "integer"
+        },
+        "denied": {
+          "type": "integer"
+        },
+        "last_allowed_at": {
+          "format": "date-time",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "last_request_at": {
+          "format": "date-time",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "requests": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "requests",
+        "allowed",
+        "denied",
+        "bytes_in",
+        "bytes_out",
+        "last_request_at",
+        "last_allowed_at"
+      ],
+      "type": "object"
+    },
+    "people_apps": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "allowed": {
+            "type": "integer"
+          },
+          "app": {
+            "type": "string"
+          },
+          "bytes_in": {
+            "type": "integer"
+          },
+          "bytes_out": {
+            "type": "integer"
+          },
+          "denied": {
+            "type": "integer"
+          },
+          "last_allowed_at": {
+            "format": "date-time",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "last_request_at": {
+            "format": "date-time",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "login": {
+            "type": "string"
+          },
+          "requests": {
+            "type": "integer"
+          },
+          "subject": {
+            "type": "string"
+          },
+          "subject_kind": {
+            "enum": [
+              "human",
+              "tagged",
+              "public",
+              "unknown"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "subject_kind",
+          "app",
+          "requests",
+          "allowed",
+          "denied",
+          "bytes_in",
+          "bytes_out",
+          "last_request_at",
+          "last_allowed_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tcp": {
+      "additionalProperties": false,
+      "properties": {
+        "allowed": {
+          "type": "integer"
+        },
+        "bytes_in": {
+          "type": "integer"
+        },
+        "bytes_out": {
+          "type": "integer"
+        },
+        "closed": {
+          "type": "integer"
+        },
+        "connections": {
+          "type": "integer"
+        },
+        "denied": {
+          "type": "integer"
+        },
+        "gate_drops": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "connections",
+        "allowed",
+        "denied",
+        "closed",
+        "bytes_in",
+        "bytes_out",
+        "gate_drops"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "http",
+    "people_apps",
+    "apps",
+    "tcp"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "count",
-  "allowed",
-  "denied",
-  "people",
-  "apps"
-]New value: +[
+  "count",
+  "allowed",
+  "denied",
+  "people",
+  "apps",
+  "traffic"
+]

First observedv0.1.0Oct 19, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations, it discloses important non-obvious behavior: summaries cover all matches regardless of the event limit, denied events do not advance last allowed access, and query strings/headers/bodies are absent. It also confirms no credentials, network calls, or writes and notes viewer-scope suitability, which adds auth context not present in annotations.

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?

The description is front-loaded with the core aggregation purpose and then adds usage, behavioral caveats, and privacy notes. It is dense but every sentence contributes; the first sentence is long yet appropriately information-rich.

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?

With an output schema present, the description needn't explain return values, and it does cover aggregation behavior and data absence well. However, for a six-parameter tool with no schema descriptions, the missing filter semantics (especially since/until formats and who/app meaning) leave notable gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden for six parameters. It mentions 'event limit' and 'denied events' in passing and references app/login as grouping dimensions, but it never explains the app, who, since, until, or decision filters or their accepted formats, leaving most parameters semantically opaque.

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 uses a specific verb (aggregate) and resource (local access events) and enumerates the resulting audit counts and traffic metrics. It clearly distinguishes itself from access_log by contrasting totals/trends with individual events, so an agent can select it without opening the schema.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool versus the sibling: 'Use access_summary for totals and trends; use access_log for individual events.' It also notes suitability for viewer scopes, giving a clear permission context.

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