Dorico Maestro

Overview Schema Source Related Servers Discussions Admin

navigate

Idempotent

Scroll the score viewport to the start or end of the current flow, leaving the caret unchanged. For reaching a specific bar, use goto_bar instead.

Instructions

Scroll the score viewport to the start or end of the flow.

Moves what is on screen through View.MoveViewportTo*, and nothing else: the
caret stays where it was and no music changes.

Returns:
    Result dictionary reporting the scroll, or the redirect for target='bar'.

Note:
    Use goto_bar instead to put the caret somewhere, which is what note entry
    needs. This tool would scroll past the bar and leave the caret behind. A
    target of 'bar' says so rather than doing half the job.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bar`	No	Bar number counted from 1, read only when target is 'bar'. Ignored for 'start' and 'end'.
`target`	Yes	Where to scroll: 'start' for the beginning of the flow, 'end' for the end. 'bar' is accepted and redirects to goto_bar, because reaching a bar means moving the caret rather than the viewport.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.2Sep 7, 2026

addedInput schema / properties / bar / description

Added value: +"Bar number counted from 1, read only when target is 'bar'. Ignored for 'start' and 'end'."

addedInput schema / properties / target / description

Added value: +"Where to scroll: 'start' for the beginning of the flow, 'end' for the end. 'bar' is accepted and redirects to goto_bar, because reaching a bar means moving the caret rather than the viewport."

First observedv0.1.0Aug 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes beyond the annotations by disclosing exactly what side effects occur: it moves on-screen content via View.MoveViewportTo*, leaves the caret untouched, and makes no music changes. It also states the return behavior, including the redirect case for target='bar'.

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 well-structured with a front-loaded summary, a returns section, and a usage note. It is slightly longer than strictly necessary because the schema already covers parameter semantics, but every sentence adds meaningful behavioral or routing context.

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 2-parameter tool with 100% schema coverage, an output schema, and annotations, the description fully covers what the tool does, when to avoid it, what it returns, and how target='bar' is handled. Nothing essential is missing for an agent to invoke 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?

The schema already fully describes both parameters, including the conditional behavior of 'bar' and the 'read only when target is bar' semantics. The description adds context by framing 'bar' as a redirect to goto_bar and explaining the rationale, which enriches the schema's documentation.

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?

The description opens with a specific verb and resource: 'Scroll the score viewport to the start or end of the flow.' It clearly distinguishes navigate from goto_bar, stating that navigate only affects the viewport while leaving the caret in place.

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?

The description explicitly instructs when not to use this tool: 'Use goto_bar instead to put the caret somewhere, which is what note entry needs.' It also explains that a target of 'bar' redirects to goto_bar rather than performing a partial viewport scroll, giving the agent clear decision criteria.

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