TimeSync MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_network_interfacesA | List local Linux interfaces with sysfs state, link speed, driver and timestamp/PHC capabilities. Ordinary user; partial evidence retained. |
| get_timestamp_capabilitiesA | Read ethtool -T for one interface. Capabilities do not prove current PTP synchronization. |
| get_ptp_statusA | Query five LinuxPTP GET datasets over configured UDS. Domain 0..127; verify interface/port association. Never starts ptp4l. |
| get_chrony_statusA | Read chronyc CSV tracking, sources and sourcestats, reporting estimated offsets in ns and frequency in ppm. |
| inspect_time_servicesA | Read systemd states and ExecStart for allowlisted time services. Coexistence alone is not adjustment conflict. |
| get_time_sync_logsA | Read bounded, redacted journald entries. since/until: timezone-aware ISO8601, at most 7 days; default last hour. Journal permission may restrict evidence. |
| get_diagnostic_capabilitiesB | Report actual runtime dependencies, command availability, optional ROS Bridge and unsupported adapters. |
| analyze_timestamp_seriesB | Analyze int64 ns intervals, repeats/backwards/jumps. Optional paired events fit offset/rate only with explicit trusted correspondence evidence; user-supplied evidence is an assertion, not independent verification. |
| inspect_clock_domainsA | Return explicitly configured clock graph, directed mappings and validity/uncertainty. No relationship is inferred from sharing a host. |
| list_ros_topicsB | Discover ROS topics/types, endpoints, QoS and Header support through the optional distribution-matched Bridge. |
| inspect_ros_topicA | Sample one topic for 0.1..30 seconds, bounded by configured sample cap; inspect Header and callback-arrival intervals separately. |
| analyze_ros_timestampsB | Analyze Header periodicity and monotonic callback arrival intervals separately. Does not infer DDS latency or physical sample jitter. |
| compare_ros_topicsB | Simultaneously sample two topics, require explicit compatible clock domains, then one-to-one exact/tolerance match. Sampling phase is not physical clock offset. |
| inspect_ros_clockB | Observe /clock progression/pause/backwards and query per-node use_sim_time read-only. Simulation time is never compared to UTC. |
| generate_time_sync_reportB | Collect live Linux evidence and deterministic findings with configurable thresholds; return JSON or Markdown with JSON evidence. No files or system settings are changed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| diagnose_ptp | Evidence-first PTP workflow. |
| diagnose_camera_imu_sync | Separate clock synchronization, Header alignment and physical sample timing. |
| diagnose_ros_timestamp_jitter | Analyze Header versus subscriber arrival jitter. |
| diagnose_robot_time_sync | Combine Linux, ROS and clock-domain evidence without changing the robot. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| rules |
TDQS
Scored across 15 tools
Each tool has a distinct resource/action target: logs, interfaces, PTP status, chrony status, services, clock domains, ROS topics, ROS clock, and report generation are cleanly separated. Even the analysis tools are differentiated by scope, such as generic timestamp series versus ROS-specific timestamp analysis.
All tools follow a consistent snake_case verb_noun pattern (get_*, list_*, inspect_*, analyze_*, compare_*, generate_*). The variety of verbs reflects different operations rather than inconsistent naming conventions.
The 15 tools are well-scoped for a read-only time-synchronization diagnostic server. Each tool maps to a specific evidence source or analysis step, and the set stays within a reasonable range without obvious filler.
The tool surface covers Linux time synchronization, PTP, chrony, clock domains, diagnostics, reporting, and ROS time analysis comprehensively. A minor gap is the lack of a generic system-clock/NTP source snapshot independent of chrony, but the existing tools provide strong workaround coverage.