Skip to main content
Glama

list_gcp_projects

Read-onlyIdempotent

The GCP projects Plutus discovered behind the connection: how many are readable, unreadable or excluded, and per project the access status, the fix when it is unreadable, and whether it is included. enabled false means multi-project coverage is off for this account. Change inclusion with set_gcp_project_included. Mirrors GET /api/accounts/:accountId/gcp/projects.

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": "list_gcp_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral context beyond them: the shape of the payload (counts plus per-project status), the meaning of the `enabled` flag, and the presence of a fix hint when a project is unreadable. It does not discuss pagination or whether results are cached, which keeps it short of a 5.

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

Conciseness4/5

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

Front-loaded with the resource and contents, then the `enabled` caveat, then the sibling pointer and endpoint reference — a sensible ordering with no filler. The phrasing is somewhat telegraphic ('the fix when it is unreadable'), which costs a little readability but not accuracy.

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

Completeness5/5

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

With no output schema present, the description carries the burden of explaining return values and does so: counts of readable/unreadable/excluded, per-project access status, remediation hint, inclusion flag, and the `enabled` account-level switch. Nothing an agent needs in order to call and interpret this zero-parameter read is missing.

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 takes zero parameters, so the baseline is 4 and there is no parameter meaning to add. The description correctly spends its words on output semantics instead of inventing inputs.

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?

States a specific resource (GCP projects discovered behind the connection) and enumerates what the listing conveys: readable/unreadable/excluded counts, per-project access status, remediation hint, and inclusion flag. It also names the sibling mutator (set_gcp_project_included) and the REST endpoint it mirrors, so an agent can tell it apart from adjacent list tools without opening a schema.

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

Usage Guidelines4/5

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

Explicitly routes mutation intent elsewhere by naming set_gcp_project_included for changing inclusion, and the 'enabled false' note signals the case where multi-project coverage is absent. There is no explicit when-not-to-call statement (e.g., use get_gcp_usage_settings for billing-side settings), but the context for calling is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources