Skip to main content
Glama
Sign In
console-mcp

console-mcp

by rohithgoud30
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

stream_simulator_logs

Stream live logs from an iOS Simulator, optionally filtering by process name. Set duration up to 30 seconds for real-time debugging.

Instructions

Stream live logs from an iOS Simulator for a duration

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

Input Schema

NameRequiredDescriptionDefault
processNoFilter by process name
simulatorYesSimulator name or UDID
durationSecondsNoHow long to stream (default: 10, max: 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It fails to state whether streaming blocks, whether it requires a running simulator, if logs are returned incrementally, or what happens after the duration. This is insufficient for a streaming tool.

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?

The description is a single sentence with no extraneous text. It is front-loaded with the action and resource, making it easy to parse.

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?

The description omits important context such as whether the tool returns logs as a stream or accumulates them, blocking behavior, and cleanup. No output schema exists, so more detail is needed for completeness.

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 each parameter has a description. The tool description does not add extra meaning beyond the schema (e.g., no sample values or cross-references to other tools). Baseline score of 3 is appropriate.

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 specifies the verb 'Stream', the resource 'live logs from an iOS Simulator', and includes a temporal scope 'for a duration'. It effectively distinguishes from sibling tools like stream_logs (generic) and get_simulator_logs (static logs).

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?

No guidance is provided on when to use this tool versus alternatives such as stream_logs or get_simulator_logs. There is no mention of prerequisites (e.g., simulator must be running) or when not to use it.

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