Skip to main content
Glama
Sign In
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_song_grid_reference

Read-onlyIdempotent

Read a meter/tempo-aware bar of straight 16ths and eighth/sixteenth triplets, including downbeats, offbeats, and advisory 4/4 genre placements. Read-only.

Instructions

Read a meter/tempo-aware bar of straight 16ths and eighth/sixteenth triplets, downbeats/offbeats and advisory 4/4 genre placements. Read-only.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "properties": {
+      "barLengthBeats": {
+        "type": "number"
+      },
+      "conventions": {
+        "anyOf": [
+          {
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "grids": {
+        "type": "object"
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "tempoBpm": {
+        "type": "number"
+      },
+      "tempoInterpretation": {
+        "type": "object"
+      },
+      "timeSignature": {
+        "type": "object"
+      },
+      "toolReferences": {
+        "type": "object"
+      }
+    },
+    "required": [
+      "stateVersion",
+      "setFingerprint",
+      "timeSignature",
+      "tempoBpm",
+      "barLengthBeats",
+      "grids",
+      "conventions",
+      "tempoInterpretation",
+      "toolReferences"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Changed2 schema fields changedv0.3.0
    • removedInput schema / required
      Removed value: -[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the trailing 'Read-only' repeats structured data and earns no credit. The description does add some value by labeling the genre placements 'advisory' (non-authoritative) and the grid 'meter/tempo-aware', implying output adapts to the song's tempo and meter.

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?

A single front-loaded sentence with no wasted filler, though the dense noun-stacking ('meter/tempo-aware bar of straight 16ths and eighth/sixteenth triplets') hurts readability slightly.

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?

With no parameters and an output schema present, the description does not need to explain return values, and annotations cover the safety profile. What remains missing is any routing guidance for an agent surrounded by dozens of other 'get_*_context/reference' siblings, which is the main completeness gap.

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 the schema imposes no semantic burden and the baseline is 4. There is nothing for the description to compensate for on this dimension.

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

Purpose3/5

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

The verb 'Read' and the resource 'song grid reference' (from the name) are present, and the description sketches the returned content (16ths, triplets, downbeats/offbeats). However, the phrasing 'meter/tempo-aware bar' and 'advisory 4/4 genre placements' is jargon-heavy and hard to parse, and it never distinguishes this from siblings like get_song_musical_context or get_live_scale_reference.

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 when-to-use statement, no prerequisites, and no named alternative among the many context/reference siblings. 'Advisory 4/4 genre placements' hints at a use case but does not tell an agent when to reach for this tool versus the other reference tools.

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