Skip to main content
Glama
Sign In
Artifact Registry MCP Server

Artifact Registry MCP Server

by Pawangunjkar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

artifact_list_repositories

Lists repositories filtered by package format and repository type across Nexus and Artifactory for supply chain discovery, helping locate target repos for upload or promotion.

Instructions

List repositories filtered by package format and repository type.

Works across both Nexus 3 (/service/rest/v1/repositories) and Artifactory (/api/repositories).

Purpose: Inspect repository topology and locate target repos for upload or promotion. When to Use: During supply chain discovery before publishing or pulling artifacts. Behavior: Read-Only query. Side Effects: None.

Args: format_filter: Filter by package format: 'maven2', 'docker', 'npm', 'pypi', 'helm', 'raw' (or 'generic') type_filter: Filter by type: 'hosted' (or 'local'), 'proxy' (or 'remote'), 'group' (or 'virtual') session_name: Session to query (default: 'default')

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

Input Schema

NameRequiredDescriptionDefault
type_filterNo
session_nameNodefault
format_filterNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

With no annotations present, the description must carry the full behavioral burden; it does declare 'Read-Only query' and 'Side Effects: None', which is the most important trait. It is silent on auth/session prerequisites (what happens if session_name is unauthenticated) and on result size or pagination, both material for a 3-param discovery call.

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 action, then Purpose/When to Use/Behavior/Args sections that are easy to scan. 'Behavior: Read-Only query' and 'Side Effects: None' are somewhat redundant with each other, but necessary given the absence of annotations.

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?

An output schema exists, so return values need not be explained, and all three parameters are documented with accepted values. The remaining gap is operational: no mention of behavior when the named session is missing or unauthenticated, nor of any result-size or pagination characteristics.

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?

Schema coverage is 0% (bare strings, no descriptions, no enums), so the description must compensate, and it does: it enumerates accepted format values ('maven2', 'docker', 'npm', 'pypi', 'helm', 'raw'/'generic'), type values with host-vs-cloud aliases ('hosted'/'local', 'proxy'/'remote', 'group'/'virtual'), and the session default. It does not state whether filters are case-insensitive or whether an empty filter returns all repositories.

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+resource ('List repositories') plus the two filter dimensions and notes it works against both Nexus 3 and Artifactory. An agent can tell what it returns without opening the schema. It does not name a sibling it could be confused with, though none of the siblings list repositories.

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?

'When to Use: During supply chain discovery before publishing or pulling artifacts' gives a clear situational trigger and implicitly ties it to artifact_upload_binary and artifact_promote_release. There is no explicit exclusion or 'use X instead' routing, so it falls short of a 5.

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