TimeSync MCP

Overview Schema Source Related Servers Discussions Admin

generate_time_sync_report

Read-onlyIdempotent

Generate a read-only time synchronization report from live Linux PTP/Chrony, PHC, and ROS 2 timestamp evidence to identify clock-domain mismatches, jitter, and drift.

Instructions

Collect live Linux evidence and deterministic findings with configurable thresholds; return JSON or Markdown with JSON evidence. No files or system settings are changed.

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

Input Schema

Name	Required	Default
`domain`	No
`format`	No	json
`topics`	No
`interface`	No
`duration_s`	No

Output Schema

Name	Required	Default
`data`	No
`error`	No
`source`	Yes
`status`	No	valid
`warnings`	No
`measurements`	No
`schema_version`	No	1.0
`observed_at_utc`	No
`measurement_kind`	No	observed

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world; the description reinforces this with 'No files or system settings are changed,' which adds modest scope context. It omits that live collection with duration_s (up to 30s) actually takes time and samples data, which is behaviorally relevant.

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?

Two tight clauses with the key safety guarantee front-loaded and no filler. 'Return or Markdown with JSON evidence' is slightly redundant but the sentence earns its place.

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

Completeness2/5

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

An output schema exists so return values needn't be explained, and annotations cover safety. However, for a 5-parameter tool at 0% schema documentation, leaving domain, topics, interface, and duration_s unexplained (and referencing nonexistent 'thresholds') makes the definition incomplete for correct invocation.

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 must carry parameter meaning, and it does not. It mentions 'configurable thresholds,' yet no threshold parameter exists in the schema, and domain, interface, topics, and duration_s are never explained — domain/topics especially need semantics an agent can't infer.

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 (collect/generate report) and resource (Linux time-sync evidence + deterministic findings), with output format noted. It does not distinguish itself from siblings like get_time_sync_logs or inspect_time_services, so an agent cannot tell when this 'report' differs from those.

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

Usage Guidelines3/5

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

'Collect live Linux evidence and deterministic findings' implies this is the aggregate/analysis tool versus raw getters, so usage is inferable. But there is no explicit when-to-use, when-not, or named alternative among the many time-sync siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server