Zachary Roth Music

Export Cyclic Scale Musicxml

export_cyclic_scale_musicxml

Read-only

Use this when an agent needs to create a bounded, two-measure MusicXML representation of a 12-division cyclic scale for local import, in the mixed, sharp, or flat accidental spelling. Do not infer ownership, licensing, or unpublished availability.

Input Schema

TableJSON Schema

Name	Required	Default
`root`	No
`modulus`	Yes
`accidentals`	No	mixed
`intervalWord`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 13, 2026

addedInput schema / properties / accidentals

Added value: +{
+  "default": "mixed",
+  "enum": [
+    "mixed",
+    "sharp",
+    "flat"
+  ],
+  "type": "string"
+}

Changed9 schema fields changedSep 2, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / intervalWord

Added value: +{
+  "items": {
+    "maximum": 16,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "maxItems": 10,
+  "minItems": 2,
+  "type": "array"
+}

addedInput schema / properties / modulus

Added value: +{
+  "const": 12,
+  "type": "number"
+}

addedInput schema / properties / root

Added value: +{
+  "default": 0,
+  "maximum": 11,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / required

Added value: +[
+  "modulus",
+  "intervalWord"
+]

addedOutput schema / additionalProperties / $ref
```
Added value: +"#/definitions/__schema0"
```

removedOutput schema / additionalProperties / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  },
-  {
-    "items": {
-      "$ref": "#/additionalProperties"
-    },
-    "type": "array"
-  },
-  {
-    "additionalProperties": {
-      "$ref": "#/additionalProperties"
-    },
-    "type": "object"
-  }
-]

addedOutput schema / definitions

Added value: +{
+  "__schema0": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      },
+      {
+        "items": {
+          "$ref": "#/definitions/__schema0"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": {
+          "$ref": "#/definitions/__schema0"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      }
+    ]
+  }
+}

First observedSep 1, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description still adds real value: the output is explicitly bounded to two measures, is intended for local import, and comes with a negative disclosure that ownership/licensing/unpublished availability must not be inferred.

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?

Two sentences with the usage trigger front-loaded and no filler. The first sentence is dense but every clause (bounded, two-measure, 12-division, local import, accidental spelling) carries information.

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 described, and the description covers the generated artifact well. The gap is on the input side: with 0% schema coverage and a required intervalWord parameter, the definition is only minimum-viable for an agent trying to supply a valid call.

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% across four parameters. The description only partially compensates, mapping "12-division" to the modulus const and "mixed, sharp, or flat" to the accidentals enum, but says nothing about root or about intervalWord — which is required and is the least self-explanatory parameter (a 2-10 item array of integers 1-16).

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 (create/export) and resource (a bounded, two-measure MusicXML representation of a 12-division cyclic scale), which a reader can distinguish from analyze_cyclic_scale, classify_cyclic_mode, and generate_cyclic_scales. It does not name any sibling directly to sharpen the boundary, so it falls just short of a 5.

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?

"Use this when an agent needs to create ... for local import" gives a concrete triggering context, and the "Do not infer ownership, licensing, or unpublished availability" line acts as a caveat. However, no alternative tool is named and no condition is given for preferring generate_cyclic_scales over this export variant, leaving routing to inference.

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

All Zachary Roth Music tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?