Skip to main content
Glama

go_to

Shows a selected shot in Dinoctor's editor so users can see the current work and set the on-screen shot used by edit tools, without changing the project.

Instructions

Show a shot in Dinoctor's editor so the person sees what you're working on. Changes only what's on screen, not the project. Edit tools use the shot on screen when no shot is given, so this also sets their default. Returns { showing }. To get a picture of the shot, use look.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe shot's id from get_project. Give this, or scene and shot. Left out: the shot on screen.
shotNoShot index from 0 inside that scene (used with scene).
sceneNoScene index from 0 (used with shot).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / id / description
      Added value: +"The shot's id from get_project. Give this, or scene and shot. Left out: the shot on screen."
    • addedInput schema / properties / scene / description
      Added value: +"Scene index from 0 (used with shot)."
    • addedInput schema / properties / shot / description
      Added value: +"Shot index from 0 inside that scene (used with scene)."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations mark this as non-read-only, non-destructive and non-open-world; the description adds real context beyond them by scoping the mutation to on-screen state rather than the project, disclosing the side effect on edit-tool defaults, and naming the return value { showing }. It stops short of saying whether repeated calls with the same id are cheap or what happens if the id is invalid, which is why it isn't a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each carrying distinct information: purpose, mutation scope, default-setting side effect, return shape, and the pointer to 'look'. The core action is front-loaded and nothing is padded.

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

Completeness5/5

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

For a three-parameter state-setting tool with no output schema, everything needed is present: the selector options are covered by the schema, the description supplies the return shape ({ showing }), the scope of the change, and the cross-tool default behavior. No obvious gap remains for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description earns an extra point by explaining the consequence of omitting the shot selector — edit tools then inherit whatever is on screen. That is operational meaning the schema only states neutrally as "Left out: the shot on screen".

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource — showing a specific shot in the editor — plus the intent (so the person sees what you're working on). It also distinguishes itself from the sibling 'look', which retrieves a picture rather than changing the visible state, so an agent can pick between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the positive trigger (when you want the person to see the shot you're working on), names the alternative explicitly ("To get a picture of the shot, use look"), and adds a non-obvious interaction rule: edit tools fall back to the shot on screen. That covers when to use, what to use instead, and the downstream effect of calling it.

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