Skip to main content
Glama

list-projects

Retrieve all Google Cloud Platform projects available with your current authentication credentials to manage and access GCP resources.

Instructions

List all GCP projects accessible with current credentials

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.ts:98-106 (registration)
    Registers the 'list-projects' tool with its description and empty input schema in the listTools response.
    {
      name: "list-projects",
      description: "List all GCP projects accessible with current credentials",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Executes the 'list-projects' tool by calling listAvailableProjects() and formatting the response.
    } else if (name === "list-projects") {
      const projects = await listAvailableProjects();
      return createTextResponse(JSON.stringify({ projects }));
  • Core logic to list accessible GCP projects using ProjectsClient.searchProjects(), with error handling.
    async function listAvailableProjects(): Promise<string[]> {
      const projectsClient = new ProjectsClient();
      
      try {
        const [projects] = await projectsClient.searchProjects();
        return projects.map((p: any) => JSON.stringify(p));
      } catch (error) {
        console.error('Error listing projects:', error);
        return [];
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a list operation but doesn't describe return format, pagination, rate limits, authentication requirements beyond 'current credentials', or error conditions. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that communicates the essential information without any wasted words. It's appropriately sized for a simple list operation and front-loads the core functionality. Every word earns its place in this concise statement.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. While it states what the tool does, it doesn't describe what the output looks like, how results are formatted, whether there are limitations, or how it differs from related tools. Given the lack of structured data, the description should provide more operational context.

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

Parameters4/5

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

The tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose. A baseline of 4 is correct for zero-parameter tools where the schema handles all parameter documentation.

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 action ('List all') and resource ('GCP projects'), making the purpose immediately understandable. It specifies the scope ('accessible with current credentials'), which adds useful context. However, it doesn't explicitly differentiate from sibling tools like 'select-project' or 'get-billing-info', preventing a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'select-project' or 'get-billing-info'. It mentions the credential scope but doesn't indicate prerequisites, typical use cases, or exclusions. Without any usage context, the agent must infer when this tool is appropriate.

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/RadiumGu/gcp-ops-mcp'

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