Skip to main content
Glama
Sign In
doricomcp

doricomcp

by kulbiq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_flow

Add a new flow (movement) at the end of a Dorico project, including all players, so you can extend a live score through conversation with a single undoable edit.

Instructions

Add a new flow (movement) at the end of the project, with all players.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose two non-obvious traits: the flow is appended at the end of the project and includes all players. It does not cover permissions, failure modes, reversibility, or what is returned, which is a significant gap for a mutation tool.

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?

A single short sentence that front-loads the action and resource, then adds the two key behavioral details. Nothing is redundant or padded.

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?

For a zero-argument creation tool with no output schema or annotations, the description covers the essential action and placement. However, it omits whether the new flow is returned and what happens to existing flows, which an agent might need for chaining or verification.

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 tool takes zero parameters, so there is no schema meaning to supplement. The baseline for a parameterless tool is 4, and the description correctly does not invent or misdescribe inputs.

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 states a specific verb and resource: 'Add a new flow (movement)' and clarifies placement 'at the end of the project, with all players.' This distinguishes it cleanly from delete_flow and rename_flow, though it does not explicitly name those 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?

Usage is implied by the name and description: call this to create a new movement. There is no explicit when-to-use vs. when-not guidance, no prerequisites, and no pointer to sibling tools, leaving the agent to infer context.

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