Skip to main content
Glama
Sign In
MCP Vibe Coding Tools

MCP Vibe Coding Tools

by ammilam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gcloud_config_set

Set a Google Cloud configuration property such as project, region, or zone to define your environment. Quickly update gcloud defaults without leaving your workflow.

Instructions

Set a gcloud configuration property (project, region, zone, etc.)

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": {
      "property": "<property>",
      "value": "<value>"
    },
    "name": "gcloud_config_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesValue to set
propertyYesProperty to set (e.g., 'project', 'compute/region', 'compute/zone')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It only says 'Set', implying mutation, but omits details like persistence, required permissions, validation behavior, or side effects. This leaves the agent uncertain about the tool's impact.

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 short sentence, which is concise but lacks structure. It fits the tool's simplicity, but could be more informative without being verbose. The sentence is front-loaded with the key action.

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?

Given no annotations and no output schema, the description is incomplete. It does not explain what the tool returns (e.g., success message), whether changes are immediate, or how errors are handled. For a simple mutation tool, more context is needed for safe use.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema, merely repeating examples. It does not explain the format or validation of property names or values.

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?

The description clearly states the tool's purpose: setting a gcloud configuration property, with examples of common properties. It distinguishes itself from siblings like gcloud_config_get and gcloud_config_list by indicating it is the write operation. However, it could be more precise about the scope (e.g., active configuration).

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. There is no mention of when not to use it, prerequisites, or comparison with gcloud_config_get/list. The agent must infer usage from context.

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