Skip to main content
Glama
harbor-mcp

harbor-mcp

by si-essence

harbor_admin

Destructive

Read Harbor quotas, labels, GC schedule/history, retention metadata, and webhook policies; create/update labels or GC schedules only with confirmed, write-enabled calls.

Instructions

Quotas, labels, GC schedule and history, retention metadata, and webhook policy list. GC schedule writes and label writes are gated. Writes run only when confirm is true and HARBOR_ALLOW_WRITES=true. Actions: quotas_list, quota_get, labels_list, label_create, label_get, label_update, label_delete, gc_schedule, gc_history, gc_schedule_create, gc_schedule_update, retention_metadata, retention_get, webhook_list, webhook_events.

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": {
      "action": "<action>"
    },
    "name": "harbor_admin"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
nameNo
pageNo
scopeNo
actionYesHarbor operation to call.
confirmNoBoolean true runs the write when HARBOR_ALLOW_WRITES is true. Omit it or pass false for a dry-run preview that sends nothing. The string true is rejected.
documentNo
label_idNo
page_sizeNo
project_name_or_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds substantive context beyond them: which write families are gated, the two-factor gate (confirm plus env var), and that omitting confirm yields a dry-run that sends nothing. It still does not disclose what label_delete or GC schedule updates destroy, nor how the gating failure manifests at call time.

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

Conciseness3/5

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

The prose is compact and the gating rules are front-loaded before the action list, which is good ordering. However, the trailing enumeration of all 15 action names duplicates the action enum in the input schema verbatim, which is pure waste in a description.

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 destructive, 15-action, 10-parameter tool with no output schema and only 20% schema coverage, the description should map parameters to actions (e.g., which of id/name/scope/document each action needs) and say what a dry-run returns. Neither is present, so an agent can select an action but will likely mis-supply its parameters.

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 20% across 10 parameters, so the description must compensate and largely does not: id, name, scope, page, page_size, document, label_id, and project_name_or_id are never explained. The confirm semantics it does state are already documented in the schema's own confirm description, so the net added meaning is near zero.

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 names the resource domains (quotas, labels, GC schedule, retention metadata, webhooks) and enumerates 15 concrete actions, so an agent can tell what is in scope. It lacks an explicit verb framing and never contrasts itself with siblings like harbor_system, which could plausibly overlap on GC or system policy.

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?

It gives a real precondition ('Writes run only when confirm is true and HARBOR_ALLOW_WRITES=true') and flags which write families are gated, which is genuine when-to-use guidance. It never says when to pick this tool over harbor_system or another sibling, and gives no per-action selection guidance among the 15 actions.

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