Skip to main content
Glama

List realm sync jobs

proxmox_list_realm_sync_jobs
Read-only

List scheduled realm sync jobs for LDAP, AD, and OpenID realms, including each job's schedule plus last and next run times, to check periodic user and group synchronization.

Instructions

List scheduled realm sync jobs (periodic LDAP/AD/OpenID user and group sync) with schedule, last and next run.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds useful behavioral context by naming the fields returned (schedule, last and next run), which is real value since there is no output schema, but it says nothing about pagination, empty results, or whether disabled jobs appear.

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?

A single front-loaded sentence with the resource, the disambiguating parenthetical, and the returned fields. No filler or repetition; every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small read-only list tool with annotations covering safety, the core purpose and returned fields are sufficient. The significant remaining gap is the two entirely undocumented parameters, which the description does nothing to cover given the 0% schema coverage.

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 0%, so the description carries the full burden for the two parameters (fields, search) — and it mentions neither. The agent gets no hint that 'fields' projects columns or that 'search' filters by name, leaving both parameters effectively undocumented.

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 and resource ("List scheduled realm sync jobs") and the parenthetical "periodic LDAP/AD/OpenID user and group sync" disambiguates realm sync from the sibling job lists like proxmox_list_backup_jobs and proxmox_list_replication_jobs. It also previews what each entry contains, though it does not explicitly say which sibling to use instead.

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

Usage Guidelines2/5

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

The description implies the use case (inspecting periodic auth sync schedules) but gives no explicit when-to-use guidance, no exclusions, and never distinguishes this from proxmox_get_realm or the other *_jobs listing tools. The agent must infer selection from the name alone.

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