Skip to main content
Glama
Sign In
vouh-chronos-mcp

vouh-chronos-mcp

by urielhgb7-arch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Analyser les mouvements et générer motion-spec.md

analyze_motion

Measure website animation timing, easing, parallax, scroll smoothing, stagger, and optical flow from a capture, then write a motion-spec.md report for reproducing and validating interface motion.

Instructions

Calcule les durées, courbes d'easing (Bézier / ressort), parallax, lissage de scroll, cascades (stagger) et flux optique, puis écrit motion-spec.md.

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": {
      "capture_id": "<capture_id>"
    },
    "name": "analyze_motion"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNoNom du fichier de rapport Markdown (défaut : 'motion-spec.md')motion-spec.md
detailNoNiveau de détail ('summary' | 'full', défaut : 'full')full
capture_idYesIdentifiant de la capture

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the key non-obvious trait: the tool writes a file (motion-spec.md). However, it omits whether an existing report is overwritten, whether the operation is expensive or long-running, and what happens when the capture has no motion data.

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?

A single front-loaded sentence that puts the computed analyses first and the output artifact last, with no filler. The dense enumeration of techniques is long but every item conveys a distinct capability.

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?

For a 3-parameter tool with no output schema and no annotations, the definition covers what is computed and that a file is produced, but leaves the report's content, the summary/full distinction's effect, and pipeline prerequisites unexplained. Adequate for invocation, thin for planning around it.

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 description coverage is 100%, so out, detail, and capture_id are already documented in the schema, making 3 the baseline. The description adds nothing about the detail levels or output naming beyond restating that motion-spec.md is written.

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 names a specific verb ('Calcule'/'écrit') and enumerates the concrete artifacts produced: durations, Bézier/spring easing, parallax, scroll smoothing, stagger, optical flow, and the motion-spec.md report. This is clearly an analysis-and-report tool, distinguishable in substance from siblings like compare_captures or build_reproduction_pack, though it never explicitly contrasts itself with them.

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?

There is no when-to-use guidance, no stated prerequisite (that a capture must first exist via capture_site/get_frames), and no mention of alternatives or when not to call it. The agent must infer the pipeline position from the required capture_id alone.

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

Deploy Server

Other Tools