Skip to main content
Glama

Server Details

Interact with your Google Cloud Composer resources using natural language commands.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 4.4/5 across 11 of 11 tools scored.

Server CoherenceA
Disambiguation5/5

Each tool has a clearly distinct purpose targeting specific Cloud Composer operations. Tools like create_environment vs delete_environment, get_dag_run vs get_task_instance, and list_environments vs get_environment all serve non-overlapping functions with clear boundaries. The descriptions reinforce these distinctions, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern with snake_case throughout. The verbs are appropriately descriptive (create, delete, get, list, find, manage) and consistently applied to their corresponding nouns (environment, operation, dag_run, task_instance, etc.). There are no deviations in naming conventions.

Tool Count5/5

With 11 tools, this server is well-scoped for Cloud Composer environment management. It covers environment lifecycle (create, delete, list, get), DAG/task operations (get_dag_run, get_task_instance, list_failed_task_instances), package management, and operation monitoring. Each tool earns its place without redundancy or obvious omissions.

Completeness4/5

The tool surface provides excellent coverage of core Cloud Composer operations including environment CRUD, DAG/task inspection, and package management. The only minor gap is the lack of tools for directly triggering DAG runs or modifying DAG code, though get_dag_source_code supports debugging. The get_operation tool effectively handles long-running operations across multiple tools.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources