Skip to main content
Glama

plan_transitions

Read-onlyIdempotent

Return implemented transition types with their timeline positions to verify available motion effects and avoid random transition assignment.

Instructions

Return implemented transition types with their timeline positions; no random transition assignment.

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

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?

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that only implemented transitions are returned and that nothing is randomly assigned, which is real behavioral context, but it is vague about what 'implemented' means and whether the result is per-project or per-timeline.

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?

One compact sentence with the purpose front-loaded and no redundant wording. The semicolon clause is slightly cryptic but earns its place by ruling out random assignment.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. The remaining gap is the undocumented required 'timeline' argument, which for a one-parameter tool is the main thing an agent needs and is absent from both schema and description.

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% for the single required 'timeline' parameter, and the description does not compensate: it mentions 'timeline positions' in the output sense but never explains what value the timeline argument should take (ID, name, path). An agent must guess the input format.

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?

Uses a specific verb ('Return') with a specific resource ('implemented transition types with their timeline positions'), which separates it from the write-side sibling create_transition. The phrase 'implemented transition types' is somewhat jargon-dependent, but the read-only reporting intent is clear.

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 clause 'no random transition assignment' implies the tool is for inspecting already-decided transitions rather than generating them, which is a useful implicit boundary against create_transition. However, it never states explicitly when to call this versus the sibling transition tools, leaving the boundary to inference.

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