Skip to main content
Glama

Sync Helm registry

sync_helm_registry
Destructive

Re-read a Helm registry's index now (the twin of ankra helm registries sync) so newly published charts and versions appear in list_available_charts; runs in the background and refuses while a sync is already in progress. Requires helm.manage.

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": {
      "registry_name": "<registry_name>"
    },
    "name": "sync_helm_registry"
  }
}

Input Schema

NameRequiredDescriptionDefault
registry_nameYesThe registry's name in Ankra.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses that the work runs in the background (async, no immediate result), that it fails fast when a sync is in flight, and that it requires the helm.manage permission. The annotations only flag non-read-only, non-idempotent and destructive; the operational and auth details are genuinely added by the description.

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

Conciseness5/5

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

One sentence, front-loaded with the action and immediately followed by the outcome, the concurrency constraint, and the permission requirement. The CLI-twin parenthetical is compact and helps agents map existing knowledge; nothing is wasted.

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?

For a one-parameter mutation with no output schema, the description covers the essential behavior: async execution, refusal on concurrent syncs, and required permission. It leaves slight ambiguity about how an agent should verify completion, which a reference to the sync-jobs sibling would have closed.

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

Parameters3/5

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

There is a single required parameter, registry_name, and the schema already documents it at 100% coverage with an explicit description. The description adds no extra meaning about the identifier (format, lookup behavior), so the baseline 3 applies.

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?

The description names a specific verb and resource ('Re-read a Helm registry's index now') and states the observable outcome: newly published charts and versions appear in list_available_charts. That downstream effect distinguishes it from adjacent listing tools without the agent needing to open another 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?

It gives a clear trigger condition (you want newly published charts to show up) and a precondition (refuses while a sync is already running). It does not point at list_helm_registry_sync_jobs for checking progress, which would have made routing complete, but the when-to-use context is unambiguous.

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.