Skip to main content
Glama

in_out

Get, set, or clear timeline In/Out marks to define exact render ranges for all, video, or audio tracks.

Instructions

Get/set/clear the timeline In/Out marks (used e.g. for rendering a range). type: all | video | audio.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "in_out"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
typeNoall
clearNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions get/set/clear operations, it does not explain permissions, side effects, whether clearing is destructive, what happens when both clear and start/end are supplied, or what the tool returns.

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 short, front-loaded with the core purpose, and avoids unnecessary wording. It is concise, though its brevity contributes to the missing parameter and behavioral details captured under other dimensions.

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?

The tool has four parameters, 0% schema description coverage, no annotations, and no output schema. The description explains only the type values and a high-level use case, leaving important details about start/end formats, clear behavior, and return values undocumented.

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 compensate for the four parameters. It only explains the 'type' parameter with enumerated values ('all | video | audio') and leaves 'start', 'end', and 'clear' without added meaning beyond their names.

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 gives a specific verb and resource: 'Get/set/clear the timeline In/Out marks.' It clearly explains the tool's purpose and even notes a typical use case for rendering a range. However, it does not differentiate this tool from any sibling alternatives.

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 description implies usage by mentioning rendering a range and listing type options, which gives contextual guidance. It does not explicitly state when to use this tool versus alternatives or when not to use it, leaving usage to inference.

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