Skip to main content
Glama
Sign In
MCP Vibe Coding Tools

MCP Vibe Coding Tools

by ammilam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gcloud_services_list

List enabled Google Cloud APIs and services for a project. Optionally view all available services instead.

Instructions

List enabled Google Cloud APIs and services for a 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": "gcloud_services_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNoProject ID (uses current project if not specified)
availableNoList available services instead of enabled ones

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It clearly indicates a read operation by using 'List', but it does not mention permissions, rate limits, return format, or the fact that the 'available' parameter can change behavior. The description adds basic context but lacks richer behavioral detail.

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?

The description is a single, concise sentence that clearly states the tool's purpose. It is front-loaded with the action verb and resource, with no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has only two optional parameters with good schema descriptions and no output schema. The description covers the core functionality, and the schema fills in the parameter details. It is complete enough for a simple list tool, though it does not mention the 'available' toggle in the description itself.

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?

The input schema already documents both parameters with full coverage. The description adds no additional meaning about the parameters beyond the schema, so the baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly specifies the action ('List') and the resource ('enabled Google Cloud APIs and services') with a project scope. It distinguishes from sibling tools like gcloud_services_enable and other list tools by focusing specifically on enabled services.

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 by indicating it lists enabled services, and the sibling gcloud_services_enable exists for enabling services. However, it does not explicitly state when to choose this tool over alternatives or provide exclusions.

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