MCP Server Tauri

Overview Schema Source Related Servers Discussions Admin

read_logs

Read-only

[Tauri Apps Only] Read logs from various sources: "console" for webview JS logs, "android" for logcat, "ios" for simulator logs, "system" for desktop logs. Requires active driver_session for console logs.

Instructions

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>"
    },
    "name": "read_logs"
  }
}

Input Schema

Name	Required	Description
`level`	No	Only return entries at this console level.
`lines`	No
`since`	No	ISO timestamp to filter logs since (e.g. 2023-10-27T10:00:00Z)
`filter`	No	Regex or keyword to filter logs
`source`	Yes	Log source: "console" for webview JS logs, "android" for logcat, "ios" for simulator, "system" for desktop
`maxChars`	No	Maximum characters in the response. Entries are truncated and the oldest are dropped to fit.
`windowId`	No	Window label for console logs (defaults to "main")
`appIdentifier`	No	App port or bundle ID for console logs. Defaults to the only connected app or the default app if multiple are connected.
`maxCharsPerEntry`	No	Maximum characters kept from each log entry.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.1Oct 14, 2026

addedInput schema / properties / level

Added value: +{
+  "description": "Only return entries at this console level.",
+  "enum": [
+    "log",
+    "debug",
+    "info",
+    "warn",
+    "error"
+  ],
+  "type": "string"
+}

addedInput schema / properties / lines / exclusiveMinimum
```
Added value: +0
```

changedInput schema / properties / lines / type

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

addedInput schema / properties / maxChars

Added value: +{
+  "default": 20000,
+  "description": "Maximum characters in the response. Entries are truncated and the oldest are dropped to fit.",
+  "maximum": 100000,
+  "minimum": 500,
+  "type": "integer"
+}

addedInput schema / properties / maxCharsPerEntry

Added value: +{
+  "default": 2000,
+  "description": "Maximum characters kept from each log entry.",
+  "maximum": 20000,
+  "minimum": 100,
+  "type": "integer"
+}

Addedv0.11.1May 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a real operational prerequisite (active driver_session required for console logs) beyond the structured data, though it says nothing about truncation behavior, which the schema covers instead.

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 bracketed platform scope is front-loaded, and the source list is compact and scannable. The trailing "at any level" phrase is mildly redundant filler, keeping it out of 5 territory.

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?

For a nine-parameter tool with high schema coverage and no output schema, the description covers source semantics and the key prerequisite. Missing only return-shape/pagination context, which the schema's maxChars descriptions partially absorb.

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 89%, so the schema already documents all nine parameters including enums and truncation semantics. The description's source enumeration largely repeats the schema's own source description and adds no syntax or default details for level, lines, or maxChars.

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?

States a specific verb and resource (read logs), scopes it ([Tauri Apps Only]), and enumerates the four sources with their meanings. An agent can distinguish it from sibling log-ish tools like ipc_get_captured or ipc_monitor without opening either schema.

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

Usage Guidelines4/5

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

"Use for debugging Tauri app issues at any level" gives clear usage context, and the driver_session prerequisite for the console source is spelled out. It stops short of naming an alternative for non-webview log needs or stating when NOT to use it, so it earns a 4 rather than a 5.

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