Skip to main content
Glama
Sign In
Flutter Lamp

Flutter Lamp

by itsonu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Export the debugging session

export_session
Read-onlyIdempotent

Capture the entire runtime session as a versioned JSON file — brief for diagnosis context, full for bug reports, offline analysis, or regression fixtures.

Instructions

The whole session as one versioned JSON artifact: metadata, per-collector health, retention, the captured events, and every diagnosis (runtime, performance, navigation, rebuilds). Use mode 'brief' for the smallest sufficient context — the diagnoses plus only the events their evidence cites — and 'full' to archive everything retained, for a bug report, offline analysis or a regression fixture. Sizes are not close: measured on a ~1,700-event session, 'brief' returned 36kB and 'full' returned 247kB — roughly 62,000 tokens, about a third of a 200k context window, so treat 'full' as something to write to a file rather than read inline. Credentials are already redacted at capture, so nothing here was ever stored raw.

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

Input Schema

NameRequiredDescriptionDefault
modeNo'brief': diagnoses plus only the cited events. 'full': everything retained.brief

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.21.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes further with measured payload sizes (36kB vs 247kB, ~62,000 tokens) and the fact that credentials are redacted at capture. These are behavioral traits an agent could not derive from the structured fields.

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-loaded with the artifact definition, then mode semantics, then the cost rationale. Every sentence earns its place; the size/token figures and redaction note are load-bearing, not padding.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing the return value and does so thoroughly (contents of the artifact, both mode shapes, size implications). Nothing an agent needs to call this correctly is missing.

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 100% and the enum already defines both modes, so the baseline is 3. The description nonetheless adds real decision-relevant meaning beyond the schema: the measured size gap between modes and the practical implication (inline vs file), enabling a smarter mode choice.

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+resource ('export the whole session as one versioned JSON artifact') and enumerates exactly what the artifact contains: metadata, per-collector health, retention, captured events, and every diagnosis category. This distinguishes it from the sibling tools that each return one slice (get_logs, get_frames, diagnose_runtime, etc.).

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

Usage Guidelines5/5

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

Explicitly routes between the two modes with concrete conditions: 'brief' for the smallest sufficient context, 'full' for bug reports, offline analysis, or a regression fixture. It even prescribes behavior ('treat full as something to write to a file rather than read inline'), which is exactly the when-to-use guidance an agent needs.

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

Deploy Server

Other Tools