Flutter Inspector MCP Server

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

No annotations are provided, so the description carries the full burden. It discloses that this is a VM service method and specifies the default port (8181), but doesn't cover critical behavioral aspects such as what information is returned, error handling, authentication needs, rate limits, or whether it's a read-only operation. This is a significant gap for a tool with no annotation coverage.

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

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

The description is concise and front-loaded, stating the purpose in the first sentence. The second sentence adds useful context about the port. There's no wasted text, but it could be slightly more structured by separating usage notes, earning a 4 instead of a perfect 5.

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

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

Given the complexity of retrieving VM information, no annotations, and no output schema, the description is incomplete. It doesn't explain what VM information is returned, the response format, or potential errors. For a tool with no structured output documentation, this leaves significant gaps for an AI agent to use it correctly.

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

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

The input schema has 100% description coverage, with the 'port' parameter clearly documented as optional for custom ports. The description adds minimal value beyond the schema by reiterating the default port (8181), but doesn't provide additional semantics like format constraints or usage examples. Baseline 3 is appropriate when schema coverage is high.

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

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

The description clearly states the tool's purpose: 'Get VM information from a Flutter app.' It specifies the verb ('Get') and resource ('VM information'), and distinguishes it as a 'VM service method, not a Flutter RPC.' However, it doesn't explicitly differentiate from sibling tools like 'get_active_ports' or 'get_supported_protocols,' which may also retrieve information, so it's not a perfect 5.

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

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

The description provides some implied usage context by mentioning it connects to the default Flutter debug port (8181) unless specified otherwise, which suggests when to use a custom port. However, it lacks explicit guidance on when to use this tool versus alternatives like 'dart_io_get_version' or other sibling tools, and doesn't mention any prerequisites or exclusions.

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