Skip to main content
Glama
Sign In
Karagöz

Karagöz

by yagizdo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Read device logs

logs
Read-only

Read the newest device log records oldest first, optionally filtered by device, app package, line count, or Unix timestamp, to inspect recent device activity.

Instructions

Read the newest device log records, oldest first. On iOS without since: the last minute, or the last hour with package. An iPhone read takes about 10 s.

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

Input Schema

NameRequiredDescriptionDefault
linesNoNumber of newest records. Default 30.
sinceNoUnix seconds on the device clock; only later records. Pass a record's time to continue.
deviceNoId or name.
packageNoOnly this app's records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered; the description adds useful operational context annotations cannot: platform-dependent default windows and a ~10 s latency on iPhone reads. It stops short of saying whether output is truncated or how large results are bounded.

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?

Three short sentences, front-loaded with the verb and resource, then defaults, then latency. Nothing is wasted or repeated from the schema.

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

Completeness4/5

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

For a four-param, read-only tool with no output schema, the description covers defaults, platform behavior, and cost. A brief note on what a returned record contains (fields, truncation) would close the remaining gap.

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

Parameters4/5

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

Schema coverage is 100%, so the per-parameter text is already documented. The description goes beyond it by describing the cross-parameter interaction between `since`, `package`, and platform (last minute vs last hour with package), which the schema does not express.

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?

States a specific verb and resource ('Read the newest device log records') plus the ordering ('oldest first'). It is clearly distinct from the control-plane siblings (tap, launch, screenshot), though it never names an alternative for log-related tasks such as `text`.

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?

Usage is only implied by the purpose; there is no explicit statement of when to prefer this over `text` or `devices`. The description does clarify the default time window behavior, which is the most likely source of misuse, but gives no exclusions.

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