Skip to main content
Glama
Sign In
doricomcp

doricomcp

by kulbiq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

go_to

Scroll Dorico's score view to a target bar or flow to navigate directly to the section you need to inspect or edit.

Instructions

Scroll Dorico's view to a bar.

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": {
      "bar": "<bar>"
    },
    "name": "go_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
barYes
flowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. 'Scroll the view' usefully implies a non-mutating viewport change, but nothing is said about persistence of the view change, error behavior for out-of-range bars, or interaction with the active flow. For a tool with zero annotation coverage, that is a substantial gap.

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

Conciseness3/5

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

One sentence with zero wasted words and the key verb front-loaded, but this is conciseness achieved by omission rather than by discipline — essential usage and parameter context is simply absent.

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 itself is simple, but with no annotations, no output schema, and 0% schema description coverage, the description leaves too much unexplained — particularly the 'flow' parameter and the effect of the view change.

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. It covers 'bar' implicitly, but the second parameter, 'flow' (default 0), is never mentioned and its meaning is undefined anywhere. Half the parameters remain opaque.

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?

States a specific verb and resource: scroll the view to a bar. That distinguishes it from the add_*/delete_* siblings, which mutate score content rather than reposition the viewport. It stops short of naming an explicit alternative, but the action is unambiguous.

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?

There is no guidance on when to use this versus any other tool, no prerequisites, and no note on what happens if the target bar does not exist. The agent must infer from the name alone that this is a navigation aid rather than an edit.

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

Deploy Server

Other Tools