Skip to main content
Glama
Sign In
console-mcp

console-mcp

by rohithgoud30
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_simulator_logs

Retrieve logs from a booted iOS Simulator to debug app behavior. Filter by process name, time range, or limit lines.

Instructions

Get logs from an iOS Simulator. The simulator must be booted.

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": {
      "simulator": "<simulator>"
    },
    "name": "get_simulator_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
processNoFilter by process/app name
maxLinesNoMaximum log lines (default: 200)
simulatorYesSimulator name or UDID (use list_simulators to find)
lastMinutesNoHow many minutes of logs to fetch (default: 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the booted precondition, but does not mention that the operation is read-only or any other behavioral traits like rate limits or required permissions.

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 short sentences (12 words) that front-load the purpose and precondition. No wasted words.

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?

The description is minimal but adequate for a simple tool. Given the number of sibling log tools, it could be improved by describing the output format or sample usage to ensure correct selection.

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%, so the description doesn't need to add much. It reinforces the simulator precondition but adds no new parameter-level meaning beyond the schema's existing descriptions.

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 clearly states the tool gets logs from an iOS Simulator, with a specific precondition (must be booted). It distinguishes itself from sibling tools like get_device_logs and stream_simulator_logs by focusing on simulator logs.

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?

The description provides a clear precondition ('simulator must be booted') and implies context for use, but does not explicitly state when to use this vs. alternatives like get_device_logs or stream_simulator_logs.

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

Deploy Server

Other Tools