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

vouh-chronos-mcp

by urielhgb7-arch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Lire un lot de frames ou planches

get_frames

Retrieve paginated batches of extracted video frames as JPEG images, contact sheets, ZIP archives, or video paths, with timestamped indexes for a given capture.

Instructions

Renvoie les frames extraites par lots paginés (images JPEG, planches contact, archive ZIP ou chemin vidéo) avec leur index horodaté.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNombre max d'éléments (défaut : 24, max : 40 images ou 6 planches)
offsetNoIndice de départ (défaut : 0)
deliveryNoMode de livraison ('images' | 'sheets' | 'zip' | 'video')
capture_idYesIdentifiant de la capture

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose pagination behavior and the four delivery modes, and hints that frames carry a timestamped index, but says nothing about permissions, whether the operation is read-only, or what happens when offset exceeds the available frames.

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 with no filler, starting with the verb and immediately qualifying scope and output formats. It is dense but every clause carries information; only a slight readability cost from packing four formats and pagination into one sentence.

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?

With no output schema and no annotations, the description does well to enumerate what comes back (images, contact sheets, ZIP, video path, timestamped index). It is still incomplete on prerequisites (must the capture be extracted first?) and on paging limits, which matter for a 4-parameter retrieval tool.

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 every parameter is already documented, including the delivery enum and the default/max values for limit. The description only echoes the delivery modes and paging concept, adding no syntax or edge-case detail beyond the schema.

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 ('Renvoie') and resource ('frames extraites') plus the paginated batch scope and the delivery formats (JPEG, planches contact, ZIP, chemin vidéo). It implicitly reads as retrieval of already-extracted frames, which separates it from extract_frames, but it never names that sibling explicitly.

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: 'frames extraites' suggests this is the read step after extraction, and 'lots paginés' suggests paging through large sets. There is no explicit statement of when to prefer this over extract_frames or analyze_motion, nor any precondition such as an existing capture_id.

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