TimeSync MCP

Overview Schema Source Related Servers Discussions Admin

get_timestamp_capabilities

Read-onlyIdempotent

Reads hardware timestamping capabilities via ethtool -T for a given interface. Use it to verify PTP hardware support before diagnosing clock synchronization.

Instructions

Read ethtool -T for one interface. Capabilities do not prove current PTP synchronization.

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": {
      "interface": "<interface>"
    },
    "name": "get_timestamp_capabilities"
  }
}

Input Schema

Name	Required	Description	Default
`interface`	Yes

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.6/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, so the safety profile is covered. The description adds one genuinely useful piece of context — that results are capability-only and not proof of synchronization — but says nothing about privileges ethtool may require or how to interpret an empty/unsupported result.

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 short sentences, zero filler, with the action stated first and the interpretive caveat second. Every clause earns its place.

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?

The tool is simple: one required parameter, an output schema present so return values need not be described, and annotations covering the safety profile. The description covers what it reads and warns about misinterpreting the output; only privilege requirements for ethtool are unaddressed.

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 coverage is 0%, so the description is the only prose source, and it says only 'for one interface'. The single `interface` parameter has a visible regex pattern in the schema that constrains the name format, so the schema carries most of the meaning; the description adds scope (one interface at a time) but no naming or format guidance.

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: read `ethtool -T` for a single interface. That is distinguishable from siblings like get_ptp_status or get_chrony_status, which report current state rather than hardware capability. It does not explicitly name which sibling to use instead, but the resource is precise.

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?

The caveat 'Capabilities do not prove current PTP synchronization' implies that this tool answers a hardware-support question and that get_ptp_status is the tool for live sync state, but that routing is left to inference rather than stated. No prerequisites or exclusions are spelled out.

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

Deploy Server