Skip to main content
Glama

analyze_visual_rhythm

Read-onlyIdempotent

Measure shot lengths, repetition, and readability timing from a timeline to assess visual rhythm without inventing aesthetic scores.

Instructions

Measure shot lengths, repetition and readability timing without inventing aesthetic scores.

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": {
      "timeline": "<timeline>"
    },
    "name": "analyze_visual_rhythm"
  }
}

Input Schema

NameRequiredDescriptionDefault
timelineYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

The annotations already cover the safety profile: readOnlyHint, idempotentHint, non-destructive, and closed-world. The description adds a useful behavioral guardrail against fabricated aesthetic scores, but it does not describe how the timeline is parsed, what assumptions the measurements make, or any limits on the analysis.

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?

The definition is a single front-loaded sentence that states the measurement scope and the anti-fabrication constraint with no filler. It is efficiently structured, though its terseness leaves important invocation details to inference.

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?

The output schema can explain return values and the annotations cover safety, so those do not need to be repeated. However, the only required input, 'timeline,' is undocumented in both the schema and the description, leaving a material gap for correct invocation of this 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?

There is one required parameter, 'timeline,' with 0% schema description coverage. The description hints that the input contains shot timing information by mentioning shot lengths and repetition, but it never defines the accepted format, such as a path, EDL, JSON structure, or list of durations, so an agent cannot confidently construct the argument.

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 uses a specific verb, 'measure,' and names concrete outputs: shot lengths, repetition, and readability timing. It also adds a negative scope clause about not inventing aesthetic scores, making the tool's intent clear, though it does not explicitly distinguish itself from sibling analysis tools.

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 phrase 'without inventing aesthetic scores' implies a boundary against subjective aesthetic scoring, which gives some usage context. However, there is no explicit guidance on when to choose this tool over alternatives such as analyze_project or analyze_rendered_frames, nor any stated prerequisites.

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