Skip to main content
Glama

Timelapse frame interval

bpj_design_timelapse_interval
Read-onlyIdempotent

Plan evenly spaced exposures spanning both endpoints from capture duration and intended playback length.

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": "<capture>",
      "play": "<play>",
      "fps": "<fps>"
    },
    "name": "bpj_design_timelapse_interval"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsYes
playYes
captureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive calculation, so the safety profile is covered. The description adds the key behavioral detail that exposures are evenly spaced and span both endpoints, but it does not describe the returned value, rounding, or edge-case handling.

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 description is a single front-loaded sentence with no filler and clear phrasing. It is compact, though the brevity leaves useful detail absent for a calculation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter calculator with no output schema, the description should explain what is produced and how the inputs interact. It provides the core concept but omits the returned interval, fps handling, and formulaic relationship, leaving the agent to infer essential behavior.

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 must carry parameter meaning, yet it mentions only capture duration and playback length. The required fps parameter is omitted from the description, and the relationship among all three inputs is not explained beyond the high-level planning purpose.

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 planning action and resource: evenly spaced exposures for a timelapse, derived from capture duration and intended playback length. It is clear about the calculation's intent, though it does not explicitly name the returned interval or distinguish it from neighboring design calculators.

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?

The description implies a timelapse-planning context but gives no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. An agent must infer usage from the tool name and parameter set alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.