Skip to main content
Glama
andyl25

Google Cloud MCP Server

by andyl25

set-project-id

Set the default Google Cloud project ID for subsequent operations in the MCP server, enabling streamlined access to services like Logging, Spanner, Monitoring, and Cloud Trace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe Google Cloud project ID to set as default

Implementation Reference

  • The asynchronous handler function for the 'set-project-id' tool. It calls setProjectId(projectId), handles errors, and returns markdown content indicating success or failure.
    async ({ projectId }, context) => {
      try {
        await setProjectId(projectId);
        
        return {
          content: [{
            type: 'text',
            text: `# Project ID Updated\n\nDefault Google Cloud project ID has been set to: \`${projectId}\`\n\nThis project ID will be used for all Google Cloud operations until changed.`
          }]
        };
      } catch (error: any) {
        // Error handling for set-project-id tool
        return {
          content: [{
            type: 'text',
            text: `# Error Setting Project ID\n\nFailed to set project ID: ${error.message}`
          }]
        };
      }
    }
  • Zod input schema for the 'set-project-id' tool defining the required projectId string parameter.
      projectId: z.string().describe('The Google Cloud project ID to set as default')
    },
  • Registration of the 'set-project-id' tool on the MCP server instance within registerProjectTools, including schema and handler.
    server.tool(
      'set-project-id',
      {
        projectId: z.string().describe('The Google Cloud project ID to set as default')
      },
      async ({ projectId }, context) => {
        try {
          await setProjectId(projectId);
          
          return {
            content: [{
              type: 'text',
              text: `# Project ID Updated\n\nDefault Google Cloud project ID has been set to: \`${projectId}\`\n\nThis project ID will be used for all Google Cloud operations until changed.`
            }]
          };
        } catch (error: any) {
          // Error handling for set-project-id tool
          return {
            content: [{
              type: 'text',
              text: `# Error Setting Project ID\n\nFailed to set project ID: ${error.message}`
            }]
          };
        }
      }
    );
  • src/index.ts:165-165 (registration)
    Top-level call to registerProjectTools(server) in the main server setup, which includes registration of the set-project-id tool.
    registerProjectTools(server);
  • Helper function setProjectId that persists the project ID using the state manager, called by the tool handler.
    export async function setProjectId(projectId: string): Promise<void> {
      // Use the state manager to set the project ID
      await stateManager.setCurrentProjectId(projectId);
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no 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?

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andyl25/googlecloud-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server