console-mcp

by rohithgoud30

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

get_device_logs

Retrieve logs from a connected iOS device. Filter by process, limit lines, or capture logs from recent minutes.

Instructions

Get logs from a connected iOS device. Requires libimobiledevice (brew install libimobiledevice)

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": {
      "device": "<device>"
    },
    "name": "get_device_logs"
  }
}

Input Schema

Name	Required	Description
`device`	Yes	Device name or UDID (use list_devices to find)
`process`	No	Filter by process/app name
`maxLines`	No	Maximum log lines (default: 200)
`lastMinutes`	No	How many minutes of logs to capture (default: 5, max: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 30, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, so description must disclose behavior. Only mentions a software dependency, not side effects, limitations, or whether the operation is read-only. Missing key behavioral traits like 'requires connected device'.

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?

Two efficient sentences with no waste. Front-loaded with the action and immediately adds a critical prerequisite.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Missing output description, no mention of execution environment (e.g., device must be connected wirelessly or via USB), and no guidance on default behavior. Incomplete for a moderate-complexity tool with 4 parameters and no output 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 coverage is 100%, and description adds no extra meaning to parameters. Baseline 3 is appropriate since the schema already documents parameters.

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?

Clear verb and resource: 'Get logs from a connected iOS device'. Distinguishes from simulator logs but doesn't explicitly differentiate from similar sibling tools like get_logs or stream_logs.

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?

Provides a prerequisite (libimobiledevice installation) but no guidance on when to use this tool over alternatives (e.g., vs get_simulator_logs or stream_logs). Lacks context about device connection requirement.

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

Deploy Server