flutter-orchestrator

Overview Schema Source Related Servers Discussions Admin

scaffold_flutter_observability

Set up crash reporting, analytics events, and latency monitoring for Flutter apps by selecting Sentry, Firebase, or Datadog with custom event names and performance tracking.

Instructions

Scaffolds Sentry/Firebase Crashlytics crash reporting, type-safe custom analytics event loggers, and HTTP request latency interceptors.

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

Input Schema

Name	Required	Description	Default
`provider`	No		sentry
`customEventNames`	No	List of analytics event names (e.g. ['checkout_started', 'payment_success']).
`enablePerformanceMonitoring`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention side effects such as file creation, configuration changes, or dependencies, nor does it indicate what the scaffolded output looks like. This is a significant gap for a scaffolding tool.

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, efficient sentence that names the core features without repetition or fluff. It is appropriately concise and front-loads the primary purpose, though it could be structured to include usage guidance without much length.

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?

For a tool with three parameters, no output schema, and no annotations, the description is incomplete. It does not specify what files or configuration are generated, how the provider differentiates implementation, or what performance monitoring means in practice. An agent cannot anticipate the tool's full effect or output.

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 coverage is only 33% (only customEventNames has a description). The tool description mentions 'type-safe custom analytics event loggers' but does not explain how the provider enum affects scaffolding behavior or what enablePerformanceMonitoring controls. The description adds little value beyond the schema.

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?

The description states a specific verb (scaffolds) with a clear resource (observability features) and names the concrete deliverables: crash reporting, analytics event loggers, and HTTP latency interceptors. This distinguishes it from sibling scaffold tools like scaffold_flutter_database or scaffold_flutter_backend, which target different domains.

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 guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusion cases. The description only states what it does, leaving the agent to infer appropriate usage from the name alone.

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