TimeSync MCP

Overview Schema Source Related Servers Discussions Admin

inspect_time_services

Read-onlyIdempotent

Read systemd states and ExecStart entries for allowlisted time services to verify service configuration and distinguish coexistence from actual clock adjustment conflicts.

Instructions

Read systemd states and ExecStart for allowlisted time services. Coexistence alone is not adjustment conflict.

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

Input Schema

Name	Required	Description	Default
No arguments

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

A3.7/5.0

Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive, closed-world nature of the tool. The description adds useful domain context by noting the scope is allowlisted time services and that coexistence alone is not an adjustment conflict, which helps the agent interpret results.

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?

The description is two short sentences with no wasted text, and the main purpose is front-loaded before the interpretive caveat.

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?

Given the rich annotations, zero-parameter schema, and existing output schema, the description is nearly complete. It explains the inspected data and a key interpretation caveat, though it could better route the agent among sibling diagnostic tools.

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

Parameters4/5

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

The tool has zero parameters, so the baseline is 4. The description appropriately does not discuss parameters because none exist.

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 states a specific verb and resource: reading systemd states and ExecStart values for allowlisted time services. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as get_chrony_status or get_ptp_status.

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 gives no explicit guidance on when to use this tool versus alternatives. The second sentence hints at interpreting coexistence versus adjustment conflict, but it does not provide usage conditions or exclusions.

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

Deploy Server