Zachary Roth Music

Get Composition

get_composition

Read-only

Use this when an agent needs to get public recordings matching a composition title. Do not infer ownership, licensing, or unpublished availability.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 2, 2026

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.2/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful context by specifying that only 'public recordings' are returned and warns against inferring ownership, licensing, or unpublished availability. This goes beyond what annotations provide without contradicting them.

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?

Two sentences with no filler. The primary use case is front-loaded, and the caution follows succinctly. Every sentence earns its place.

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?

Given the ambiguity around the 'id' parameter and the mismatch with 'composition title', the description is incomplete for safe invocation. An agent cannot confidently determine what identifier to provide. The existence of an output schema does not mitigate this input-side gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one parameter, 'id', with no description (0% schema coverage), so the description must explain it. It does not; further, the description mentions 'composition title' but the parameter is 'id', creating confusion about what to pass. No guidance is given on what the id represents or how to obtain it.

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 description states a specific verb and resource ('get public recordings matching a composition title'), but the tool name is 'get_composition' and the input schema takes a single 'id', not a title. This mismatch makes it unclear whether the tool retrieves compositions or recordings, and how the id relates to the described behavior. It does not strongly differentiate from sibling tools like get_release or get_track.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description opens with an explicit 'Use this when...' trigger, giving clear context for when the tool is appropriate. The additional instruction 'Do not infer ownership, licensing, or unpublished availability' provides a useful boundary. However, it does not mention alternative siblings or conditions for choosing another tool.

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?