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

apple-log-mcp

by BBC6BAE9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

apple_read_live_logs

Retrieve recent or incremental log entries from an active Apple log capture session. Filter by source or content to isolate relevant diagnostics.

Instructions

Read recent or incremental lines from a live Apple log capture session.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "apple_read_live_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sourceNoall
containsNo
sessionIdYes
sinceSequenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Without annotations, the description should disclose side effects, authentication needs, or error cases. It only mentions reading and incremental lines, but omits behavioral details like session validity or that it's a read-only operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, which is efficient but lacks necessary detail. It could be improved by adding parameter guidance while maintaining brevity.

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?

Given the tool has 5 parameters, no output schema, and no annotations, the description is too sparse. It does not explain the relationship between parameters like sinceSequence and incremental reading, or how to interpret results.

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?

No parameters are described in the schema or the description. With 0% schema coverage, the description should explain key parameters like sessionId, limit, source, contains, and sinceSequence, but it does not.

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 reads recent or incremental lines from a live Apple log capture session, which precisely distinguishes it from sibling tools that list, start, or stop sessions.

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 starting a session first or reading from a different source. The description only states the action without usage context.

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