TimeSync MCP

Overview Schema Source Related Servers Discussions Admin

analyze_timestamp_series

Read-onlyIdempotent

Analyze int64 nanosecond timestamp series to detect repeats, backward steps, and jumps, and optionally fit offset/rate from paired events when trusted correspondence evidence is supplied.

Instructions

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.

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": {
      "timestamps_ns": "<timestamps_ns>"
    },
    "name": "analyze_timestamp_series"
  }
}

Input Schema

Name	Required	Description	Default
`synthetic`	No
`timestamps_ns`	Yes
`expected_rate_hz`	No
`paired_timestamps_ns`	No
`correspondence_method`	No
`correspondence_evidence`	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.4/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description's job is to add trust semantics — and it does: user-supplied evidence is explicitly called an assertion rather than independent verification, which tells the agent how to interpret results from the paired-events path. Return format is left to the output schema, which is acceptable.

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 sentences with no filler, and the core capability is front-loaded. The telegraphic phrasing ('repeats/backwards/jumps') is dense but still decodeable.

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?

An output schema exists, so return values need not be described, and annotations cover safety. What remains missing is parameter-level detail for synthetic/rate and any sibling differentiation, making the definition merely adequate for a 6-parameter analysis tool.

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, yet it never mentions 'synthetic' or 'expected_rate_hz' by name and does not explain the correspondence_method enum choices. It adds real meaning for timestamps_ns units, paired events, and evidence trust, but at 6 parameters it leaves substantial gaps.

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 ('Analyze int64 ns intervals') and enumerates the anomalies it detects (repeats/backwards/jumps). It does not distinguish itself from the sibling analyze_ros_timestamps, so an agent must infer which analyzer to pick.

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?

Usage is only implied by the detection list, and the one explicit condition — paired fit allowed 'only with explicit trusted correspondence evidence' — is a constraint, not a routing rule. No when-to-use/when-not-to-use guidance versus analyze_ros_timestamps or compare_ros_topics is given.

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

Deploy Server