MCP Mobile Server

flutter_dev_session

Set up Flutter development sessions by checking environment, listing devices, selecting optimal hardware, and running projects with hot reload for efficient mobile app development.

Instructions

Complete Flutter dev setup: check env, list devices, select best device, run with hot reload

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": {
      "cwd": "<cwd>"
    },
    "name": "flutter_dev_session"
  }
}

Input Schema

Name	Required	Description
`cwd`	Yes	Working directory (Flutter project root)
`target`	No	Target dart file (e.g., lib/main.dart)
`preferPhysical`	No	Prefer physical device over emulator

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 7, 2025

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions actions like 'run with hot reload' but lacks details on permissions needed, whether it modifies files, error handling, or output format. For a multi-step setup tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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?

The description is a single, efficient sentence that front-loads the main purpose ('Complete Flutter dev setup') followed by key actions. Every phrase earns its place with no wasted words, making it easy to scan and understand quickly.

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?

Given the tool's complexity (multi-step setup) and lack of annotations or output schema, the description is minimally adequate. It outlines the sequence of actions but misses details like what 'best device' means, how errors are handled, or what the output contains. It meets basic needs but leaves gaps for an agent to operate effectively.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all three parameters. The description doesn't add any parameter-specific information beyond what's in the schema, such as explaining how 'preferPhysical' affects device selection. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the tool's purpose with specific verbs ('check env, list devices, select best device, run with hot reload') and identifies the resource as Flutter development setup. It distinguishes from siblings like 'flutter_run' by emphasizing comprehensive setup rather than just execution, though it doesn't explicitly name alternatives.

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?

The description implies usage context ('Complete Flutter dev setup') but doesn't explicitly state when to use this tool versus alternatives like 'flutter_run' or 'flutter_setup_environment'. No exclusions or prerequisites are mentioned, leaving the agent to infer based on the described functionality.

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