Skip to main content
Glama

Get App Logs

get_app_logs
Read-onlyIdempotent

Retrieve captured stdout and stderr logs for an application process by PID to debug GUI app behavior, with a configurable number of lines returned.

Instructions

Retrieves captured stdout and stderr execution logs for an application process.

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

Input Schema

NameRequiredDescriptionDefault
pidNo
linesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds useful context that the logs are captured stdout/stderr tied to an application process, but says nothing about buffering, whether logs persist after termination, or whether an empty result is possible. With annotations carrying the safety burden, a 3 is appropriate.

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

Conciseness4/5

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

A single front-loaded sentence with no filler or redundant restatement of the title. It is efficient, though its brevity is part of why the parameter and usage gaps remain unfilled.

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?

An output schema exists, so return values need not be explained in prose, and annotations cover safety. What is missing is behavior for the nullable pid default and the lines truncation limit, which are exactly the decisions an agent must make before calling this tool.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters. The description only weakly implies that the process identifier selects the target ('for an application process') and never explains the meaning of 'lines' (default 50) or the critical case of pid being nullable with a null default — presumably the current or most recent app, but that is left to inference.

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?

The description gives a specific verb ('Retrieves') and resource ('captured stdout and stderr execution logs') scoped to an application process, which clearly distinguishes it from lifecycle siblings like launch_app or terminate_app. It does not, however, explicitly contrast itself with any named alternative, so a 4 rather than a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. the app must be running), and no routing to siblings such as watch_ui_events or inspect_ui_tree for other diagnostic needs. The only usage signal is the implicit 'logs are for debugging' inference an agent must make itself.

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