Skip to main content
Glama
Sign In
Firebase Emulator MCP Server

Firebase Emulator MCP Server

by LaishGlenberg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

firestore_query

Query Firestore collections in the Firebase emulator to inspect local data. Filter results by field, value, and operator, and limit the number of documents returned.

Instructions

Query documents in a Firestore collection

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": {
      "collection": "<collection>"
    },
    "name": "firestore_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
collectionYes
whereFieldNo
whereValueNo
whereOperatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

D1.9/5.0
Behavior1/5

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 only says 'Query documents,' which is essentially a reuse of the tool name. It does not disclose whether the operation is read-only, whether authentication is needed, what the return format is, or any rate limits or side effects. This is severely lacking behavioral transparency.

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

Conciseness3/5

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

The description is a single sentence with no wasted words, which is structurally concise. However, it is under-specified to the point of being minimally helpful. It is neither overly long nor confusing, but it also lacks the substance expected of a tool description.

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

Completeness1/5

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

With 5 parameters, no output schema, and no annotations, the description needs to explain how the query works, what input constraints exist, and what results look like. The single sentence covers only the high-level action, leaving out all necessary operational details. This is highly incomplete.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate by explaining the parameters. It mentions none of the five parameters (collection, limit, whereField, whereValue, whereOperator). The description adds no meaning beyond the empty property names in the schema.

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

Purpose3/5

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

The description states the verb 'Query' and the resource 'documents in a Firestore collection,' making the basic purpose understandable. However, it does not distinguish this from the sibling tool 'firestore_get' (which likely retrieves a single document) or clarify that querying involves filters. It is clear but lacks sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'firestore_get' or 'firestore_list_collections.' There are no context clues, exclusions, or alternative mentions. The description gives the agent no help in tool selection.

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