google-cloud-console-mcp

Create Artifact Registry repository

ar_create_repository

Create a new Artifact Registry repository for Docker, Maven, npm, Python, apt, yum, Go, or generic packages in a chosen Google Cloud location.

Instructions

Creates a new Artifact Registry repository (docker, maven, npm, python, apt, yum, go, generic, ...).

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": {
      "location": "<location>",
      "repositoryId": "<repositoryId>"
    },
    "name": "ar_create_repository"
  }
}

Input Schema

Name	Required	Description	Default
`format`	No		DOCKER
`location`	Yes	Region, e.g. "us-central1", or "us" for a multi-region
`projectId`	No	GCP project id; defaults to GOOGLE_CLOUD_PROJECT env var
`description`	No
`repositoryId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. 'Creates' implies a write, but it says nothing about required permissions, whether the format choice is immutable after creation, duplicate-name behavior, or side effects. The format list is already covered by the schema enum.

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?

One sentence, front-loaded with the core action, with no filler. The trailing format enumeration is mildly redundant with the schema enum but does not bloat the text.

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 5-parameter mutation tool with 40% schema coverage, no annotations, and no output schema, a single sentence is insufficient. Critical call-time details (location format, project defaulting, format immutability, permission requirements) are absent.

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

Parameters2/5

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

Schema description coverage is only 40%, so the description must compensate, yet it only echoes the format values already present in the enum. It adds no meaning for location, repositoryId, projectId, or description, leaving half the parameters undocumented in both schema and text.

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?

States a specific verb and resource ('Creates a new Artifact Registry repository'), and the parenthetical enumerates supported formats, so the agent knows exactly what is produced. It is easily separable from ar_list_repositories and ar_delete_repository, though it does not explicitly name those siblings.

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?

There is no guidance on when to use this versus alternatives, nor any prerequisites (project must exist, location/region semantics, required IAM permissions). The agent is left to infer all preconditions.

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

Deploy Server