Skip to main content
Glama

gc_log

Read and filter a Dolphin emulator instance's log to diagnose crashes, OSReport output, or warnings; use grep and tail to isolate relevant lines.

Instructions

Read this instance's Dolphin log file (<user_dir>/dolphin.log).

Useful for diagnosing crashes, OSReport output from the ROM, or emulator warnings. grep keeps only lines containing the (case-insensitive) substring. tail returns only the last tail lines of the (possibly filtered) output. Returns the matching lines and some metadata.

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": {
      "instance_id": "<instance_id>"
    },
    "name": "gc_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
grepNo
tailNo
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does reasonably well: "Read" signals a non-mutating operation, and it explains that grep is case-insensitive substring matching and that tail applies to the already-filtered output, which is a real behavioral detail an agent could get wrong. Gaps remain around what happens when the log is absent, whether output is truncated, or any size limits.

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?

Front-loads the core action and file location, then covers purpose and the two filters in three tight sentences with no filler. Every sentence carries information.

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?

For a low-complexity three-parameter tool this is close to sufficient, but with no output schema the return value is described only as "the matching lines and some metadata", which is too vague for an agent to plan parsing. Error behavior for a missing or empty log file is also unstated.

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 description coverage is 0%, so the description must compensate, and it explains grep (case-insensitive substring) and tail (last N lines of the possibly filtered output) with more precision than the bare property names. instance_id is only implied by "this instance's", leaving one required parameter without explicit semantics.

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?

States a specific verb and resource ("Read this instance's Dolphin log file") and even gives the concrete path ``<user_dir>/dolphin.log``. No sibling tool reads logs, so the agent can immediately distinguish this from the config, controller, and hardware tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear when-to-use context: diagnosing crashes, OSReport output from the ROM, and emulator warnings. It stops short of explicit exclusions or naming an alternative tool for log-adjacent needs, but the use case is unambiguous.

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