Skip to main content
Glama

List Helm registry sync jobs

list_helm_registry_sync_jobs
Read-only

The sync jobs of one Helm registry (the twin of ankra helm registries sync-jobs): when each ran, its status and what it indexed. Use this when a chart or version is missing from list_available_charts to see whether the registry synced. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1).
statusNoOnly jobs in this status (for example pending, running, completed, failed).
page_sizeNoRows per page (default 50).
registry_nameYesThe registry's name in Ankra.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The readOnlyHint annotation already declares the safety profile, and 'Read-only.' merely restates it with no added credit. The description does add real behavioral value beyond annotations by describing the contents of each returned job record, which matters because there is no output schema; it says nothing about pagination defaults or ordering.

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?

Two compact sentences with no waste: the resource and its contents come first, then the diagnostic use case. Every clause earns its place and nothing is buried.

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 simple paginated read with fully documented parameters and no output schema, the description covers what the tool does, what it returns, and why an agent would call it. Only minor gaps remain, such as result ordering and whether jobs are limited to recent runs.

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?

Schema description coverage is 100%, so page, page_size, status, and registry_name are already documented in the schema. The description adds no syntax, format, or filtering nuance beyond that, so the baseline of 3 applies.

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 a specific resource (sync jobs of one Helm registry) and enumerates the fields each job exposes (when it ran, its status, what it indexed). It also ties itself to the CLI twin and to list_available_charts, so an agent can place it precisely among siblings, though the opening is a noun phrase rather than an explicit verb like 'list'.

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 concrete trigger: use this when a chart or version is missing from list_available_charts to check whether the registry synced. That is a clear when-to-use with a named alternative, but it stops short of stating when not to use it (e.g., to trigger a sync, use sync_helm_registry instead).

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.