Skip to main content
Glama
rahulkr
by rahulkr

get_flutter_logs

Retrieve Flutter-specific logs from Android devices to debug Flutter applications during development and testing workflows.

Instructions

Get Flutter-specific logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNo
device_serialNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_flutter_logs' tool. It retrieves recent logcat logs and filters them for Flutter/Dart related entries using specified keywords. Registered via @mcp.tool() decorator.
    @mcp.tool()
    def get_flutter_logs(lines: int = 100, device_serial: str | None = None) -> str:
        """Get Flutter-specific logs"""
        output = run_adb(["shell", "logcat", "-d", "-t", str(lines)], device_serial)
        
        # Filter for Flutter-related logs
        flutter_keywords = ['flutter', 'dart', 'FlutterEngine', 'FlutterActivity']
        log_lines = output.split('\n')
        flutter_lines = [l for l in log_lines 
                         if any(kw.lower() in l.lower() for kw in flutter_keywords)]
        
        return '\n'.join(flutter_lines) if flutter_lines else "No Flutter logs found"
Behavior1/5

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

No annotations are provided, so the description carries full burden but offers no behavioral details. It doesn't disclose if this is read-only, destructive, requires permissions, has rate limits, or describes output format (though an output schema exists). The description is too vague to inform agent behavior.

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?

The description is a single, concise sentence with no wasted words. However, it's under-specified rather than efficiently informative, lacking necessary details for a tool with parameters and siblings.

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 2 parameters with 0% schema coverage, no annotations, and sibling tools, the description is incomplete. It doesn't clarify the tool's role in the context of other logging tools or provide enough detail for effective use, though the output schema may help with return values.

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?

Schema description coverage is 0%, and the description adds no parameter information. It doesn't explain what 'lines' or 'device_serial' mean, their defaults, or how they affect log retrieval. With 2 undocumented parameters, the description fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get Flutter-specific logs' restates the tool name 'get_flutter_logs' with minimal elaboration, making it tautological. It specifies the resource ('Flutter-specific logs') but lacks a clear verb beyond 'Get' and doesn't differentiate from sibling logging tools like 'get_logcat' or 'get_crash_logs'.

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

Usage Guidelines1/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. It doesn't mention context (e.g., debugging Flutter apps), prerequisites, or comparisons to sibling tools like 'get_logcat' for general logs or 'get_crash_logs' for crashes.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rahulkr/r_adb_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server