Skip to main content
Glama

Run registry retention

run_registry_retention
Destructive

Start the organisation's image registry retention now instead of at its daily time, for every registry project: images the retention policy does not keep are deleted (the newest image of every repository and images pulled in the last 7 days are always kept). Use it after set_registry_retention when the registry is full and a push is blocked. Deleting images does not lower usage at once: the space comes back at the registry's weekly garbage collection (Sunday 03:00 UTC), so say that instead of promising room now. Requires credentials.write.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true / idempotentHint=false annotations by naming exactly what is destroyed (images the policy does not keep), what is protected (newest image per repository, images pulled in the last 7 days), the delayed reclamation via weekly GC at Sunday 03:00 UTC, and the credentials.write requirement.

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 and scope, then the deletion rules, then the usage trigger, then the timing caveat. Dense but each clause carries real information; the closing 'so say that instead of promising room now' is slightly conversational yet serves as correct agent-facing coaching.

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?

For a zero-parameter, no-output-schema, destructive mutation, the agent needs side effects, safeguards, timing of reclamation, and auth — all present. Nothing required to call this safely and describe the result accurately 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 no parameters, so the schema carries all there is to say and the baseline of 4 applies. The description adds scope semantics instead, clarifying that the action applies to every registry project with no way to narrow it.

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 verb (start/run retention now), the resource (organisation image registry, across every registry project), and the deviation from the default schedule (daily time). It also cleanly distinguishes itself from the adjacent sibling set_registry_retention, which configures the policy rather than executing it.

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

Usage Guidelines5/5

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

Gives an explicit trigger: use after set_registry_retention, when the registry is full and a push is blocked. It also names the correct alternative behaviour (wait for weekly garbage collection) rather than letting the agent overpromise immediate free space.

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.