@google-cloud/observability-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @google-cloud/observability-mcp@0.2.3
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
1 tool with commands in capitals or very long text
- Gives the agent orders in
list_group_stats:r queries asking to "find errors", or "show me errors", you MUST use list_log_entries tool. CRITICAL: Default to other tooling for generic questions about erro
Common and usually harmless: it is how many makers stress how a tool should be used.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
list_log_entries resourceNames, filter, orderBy, pageSize, pageToken
Use this as the primary tool to search and retrieve log entries from Google Cloud Logging.
It's essential for debugging application behavior, finding specific error messages, or auditing events.
The 'filter' is powerful and can be used to select logs by severity, resource type, text content, and more.
list_log_names parent, pageSize, pageToken
Use this as the primary tool to list the log names in a Google Cloud project.
This is useful for discovering what logs are available for a project.
Only logs which have log entries will be listed.list_buckets parent, pageSize, pageToken
Use this as the primary tool to list the log buckets in a Google Cloud project.
Log buckets are containers that store and organize your log data.
This tool is useful for understanding how your logs are stored and for managing your logging configurations.list_views parent, pageSize, pageToken
Use this as the primary tool to list the log views in a given log bucket.
Log views provide fine-grained access control to the logs in your buckets.
This is useful for managing who has access to which logs.list_sinks parent, pageSize, pageToken
Use this as the primary tool to list the log sinks in a Google Cloud project.
Log sinks control how Cloud Logging routes your logs to supported destinations, such as Cloud Storage buckets, BigQuery datasets, or Pub/Sub topics.
This is useful for understanding your logging export configurations.8 more tools
list_log_scopes parent, pageSize, pageToken
Use this as the primary tool to list the log scopes in a Google Cloud project.
Log scopes allow you to query logs from multiple projects in a single view.
This is useful for centralized logging across a large organization.list_metric_descriptors name, filter, pageSize, pageToken
Use this as the primary tool to discover the types of metrics available in a Google Cloud project.
This is a good first step to understanding what data is available for monitoring and building dashboards or alerts.list_time_series name, filter, interval, aggregation, pageSize, pageToken
Use this as the primary tool to retrieve metric data over a specific time period.
This is the core tool for monitoring and observability, allowing you to get the actual data points for a given metric.list_alert_policies name, filter, orderBy, pageSize, pageToken
Use this as the primary tool to list the alerting policies in a Google Cloud project.
Alerting policies define the conditions under which you want to be notified about issues with your services.
This is useful for understanding what alerts are currently configured.list_alerts parent, filter, orderBy, pageSize, pageToken
Use this as the primary tool to list the alerts in a Google Cloud project.
An alert is the representation of a violation of an alert policy.
This is useful for understanding current and past violations of an alert policy.list_traces projectId, filter, orderBy, pageSize, pageToken, startTime, endTime
Use this as the primary tool to retrieve and examine distributed traces from Google Cloud Trace.
Traces provide a detailed view of the path of a request as it travels through your application's services.
This is essential for understanding latency issues and debugging complex, multi-service workflows.
This will only return the root trace span, to gather full information call get_trace with that id.get_trace projectId, traceId
Use this as the primary tool to retrieve a single distributed trace from Google Cloud Trace.
Traces provide a detailed view of the path of a request as it travels through your application's services.
This is essential for understanding latency issues and debugging complex, multi-service workflows.
This is often used as a follow on to list_traces to get full details on a specific trace.list_group_stats projectName, timeRangePeriod, order, pageSize, pageToken
Use this tool ONLY to find and analyze recurring stack traces in your application.
It aggregates similar stack traces, providing statistics like the number of occurrences and the number of affected users.
DO NOT use this tool for general error searches or to view individual error logs. For queries asking to "find errors", or "show me errors", you MUST use list_log_entries tool.
CRITICAL: Default to other tooling for generic questions about errors.Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | Apache-2.0 |
|---|---|
| Needs | not stated |
| Source | github.com/googleapis/gcloud-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-Pn7JNA2PF168jUp196Jj9xwSdTtfcIu43Cqeaxh2O4oLMBAcjjK45K6zWvimWBOMuifJaUvtoSt+cLnZIdYpgw== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40google-cloud/observability-mcp)
New version out? Ask for a fresh report.