Skip to main content
Glama
Sign In
Firebase Emulator MCP Server

Firebase Emulator MCP Server

by LaishGlenberg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

emulator_logs

Get recent Firebase emulator logs via WebSocket to inspect local app behavior and diagnose errors.

Instructions

Stream recent log entries from the Firebase emulator hub WebSocket (ws://127.0.0.1:4500/)

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

Input Schema

NameRequiredDescriptionDefault
linesNoNumber of recent log entries to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It reveals the transport and endpoint, but does not explain whether the stream is continuous or one-shot, what the output format is, or any side effects. The word 'stream' may even conflict with the 'lines' parameter, which suggests a finite return, creating ambiguity.

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 sentence, front-loaded with the action and resource, and includes the endpoint. Every word provides useful information with no redundant filler.

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?

The tool has no output schema, and the description does not explain what the returned log entries look like or how the streaming behavior terminates. The ambiguity between 'stream' and the 'lines' parameter leaves a completeness gap for an agent invoking the tool.

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 coverage is 100% because the only parameter, 'lines', has a clear description in the schema. The tool description itself adds no additional parameter meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 clearly states a specific action ('Stream recent log entries') and resource ('Firebase emulator hub WebSocket') with an explicit endpoint. This distinguishes it from sibling tools like emulator_status, which focuses on status rather than logs.

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 use for retrieving emulator logs but does not explicitly state when to use this tool vs alternatives or any exclusions. It names the resource and action, giving context, but lacks clear 'when to use' guidance.

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