Skip to main content
Glama
Sign In
google-cloud-console-mcp

google-cloud-console-mcp

by kutleloove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Firebase Android apps

firebase_list_android_apps

List all Android apps registered under a Firebase project to audit or manage app registrations by project ID.

Instructions

Lists the Android apps registered under a Firebase project.

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

Input Schema

NameRequiredDescriptionDefault
pageTokenNo
projectIdNoGCP/Firebase project id; defaults to GOOGLE_CLOUD_PROJECT env var

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/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. Beyond stating it lists apps, it says nothing about pagination behavior (despite a pageToken parameter), permissions required, return shape, or whether results are scoped automatically. This leaves significant behavioral gaps for the agent.

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?

A single, front-loaded sentence with zero waste. It states the action and scope efficiently without redundancy.

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 no annotations, no output schema, and an undocumented pagination parameter, the description is too sparse. It should at least hint at pagination or the fixed Android scope to fully equip the agent.

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?

The schema documents projectId at 50% coverage but leaves pageToken completely undescribed. Without annotations, the description should compensate, yet it mentions no parameters. The pagination parameter's role is wholly undocumented, which limits correct invocation on large result sets.

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

Purpose4/5

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

States a specific verb (Lists) and resource (Android apps registered under a Firebase project). It parallels siblings like firebase_list_ios_apps and firebase_list_web_apps, making the platform scope clear, though it doesn't explicitly name the sibling distinctions.

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 usage (when you need to see Android apps in a project) but gives no explicit when-to-use or when-not-to-use guidance relative to the iOS/web list siblings. For a simple read operation this minimal guidance is adequate but not strong.

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