Skip to main content
Glama
Sign In
apple-log-mcp

apple-log-mcp

by BBC6BAE9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

apple_list_devices

List all physical and simulated Apple devices recognized by Xcode for log capture and diagnostics.

Instructions

List physical and simulated Apple devices known to Xcode/CoreDevice.

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

Input Schema

NameRequiredDescriptionDefault
includePhysicalNo
includeSimulatorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 full burden. The description indicates a read-only listing operation, which is non-destructive. However, it does not disclose any additional behavioral traits such as authentication requirements, error conditions, or performance considerations.

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, well-structured sentence that immediately conveys the tool's purpose with no unnecessary words.

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 is too minimal for a tool with two parameters. It does not explain parameter semantics, output format, or any limits. Given the lack of annotations and output schema, more context is needed for an agent to use the tool effectively.

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

Parameters1/5

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

The input schema has two boolean parameters (includePhysical, includeSimulators) with 0% schema description coverage, but the tool description does not explain their purpose or effect. The agent receives no guidance on how to filter results using these parameters.

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 lists Apple devices, using a specific verb ('List') and resource ('physical and simulated Apple devices'). It distinguishes itself from the sibling tools, which all deal with log sessions or logs, not devices.

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?

No explicit guidance on when to use this tool versus alternatives. The distinction from siblings is implicit based on topic (devices vs. logs), but no when-to-use or when-not-to-use advice is provided.

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